Memberships [ 1 ] [+]
Activity Stream [+]
Ideas Contributed [ 5 ] [+]
Limited English Proficiency considerations should extend to those segments of the population that are illiterate or who read at lower-than-average-levels.
In what cases is non-lingual content more appropriate? Could a well-designed infographic convey instructions just as well as a paragraph of text?
Would video be a sufficient compliment or supplement to text narrative?
To the greatest extent possible, invest in staff, tools, and technology that can be used on various websites, regardless of the language in which they are written. Try to roll out improvements, upgrades, and systems multilaterally. Change internal perceptions of non-English websites as tertiary investments that are usually the first on the chopping block. Consider your multilingual properties as central and crucial ...more »
Allow me to narrow search results by my zip code, or create a Search.usa.gov account that remembers my personal info (like age, zip code, search preferences) and returns specialized results based on that.
In the spirit of a common experience, create and implement a standard error page for every federal .gov website that is decommissioned, archived, or otherwise removed from public access. Offer a friendly, plain-language explanation, the ability to search all .gov websites, and perhaps a link to USA.gov and / or a centralized .gov archive. This will prevent ISPs from serving ads when a user goes to a .gov website that ...more »
Focus more on enabling task completion from start-to-finish online. Recruit developers who are "get" public policy, have the skills and freedom to experiment, and give them the tools to create.
Barring emergencies, there is virtually no content that's left to be created. Let's refine the existing content, manage the creation of new content, and put some muscle into online services.