Here is the text we could read:
PA Court Interpreters -
Removing Language Barriers
info
P A C O U R T S
Court interpreter –
A trained language professional
who facilitates communication
and access to court services for
limited English speakers by
orally interpreting or signing.
In 2020 …
30,206
interpreter
requests
were
made.
231
37
interpreters
representing
languages were on
the courts’ statewide roster.
$3.7
million
was spent
on interpreter
requests.
83%
of interpreter
requests were for
Spanish
interpreters.
Top 10 languages requested
in 2020:
1. Spanish
25,067
2. American
Sign Language
761
3. Chinese-
Mandarin
713
4. Nepali
710
5. Russian
700
6. Arabic
640
7. Vietnamese
371
8. Portuguese
302
9. Haitian
Creole
209
10. Korean
185
Top 10 counties requesting
interpreters in 2020:
Berks
3,420
York
2,215
Dauphin
1,820
Philadelphia
1,598
Luzerne
1,570
Lancaster
1,535
Lebanon
1,300
Montgomery
1,245
Bucks
1,153
Chester
1,077
Data was extracted from the Language Access Data Collection application and may reflect an underreporting
of the number of encounters and/or costs associated with the provision of language services.
infoShare_Language_Access_21
This info page is part of the LIT Lab's Form Explorer project. It is not associated with the Pennsylvania state courts.
To learn more about the project, check out our about page.
Downloads: You can download both the original form (last checked 2023-03)
and the machine-processed form with normalized data fields.
About This Form:
- Sourced from www.pacourts.us (2023-03)
- Page(s): 1
- Fields(s): 1
- Average fields per page: 1
- Reading Level: Grade 11
- LIST Grouping(s):
Unknown
Use our Rate My PDF tool to learn more.
Go beyond the above insights and learn more about this or any pdf form at
RateMyPDF.com, includes: counts of difficult words used,
passive voice decetion, and suggestions for how to make the form more usable.
Identified Data Fields:
We have done our best to automaticly identify and name form fields according to our naming conventions.
When possible, we've used names tied to our question library. See e.g., user1_name.
If we think we've found a match to a question in our library, it is highlighted in green. Novel names are auto generated. So, you will probably need to edit some of them if you're trying to stick to the convention.
Here are the fields we could identify.
info
was info (0.57 conf)
We've done our best to group similar variables togther to avoid overwhelming the user.
Create an Interactive Version of this Form:
The Weaver creates a draft guided interview from a template form, like the one provided here. You can use the link below to open this form in the Weaver.
To learn more, read "Weaving" your form into a draft interview.
Launch Form in Weaver