DPSS ePolicy

To release a new policy.

This policy outlines the technical requirements to establish a website that is accessible, usable, and inclusive for individuals with disabilities.  Creating accessible content allows the customers of the Department of Public Social Services (DPSS), equal access to the programs and services offered.  DPSS and its contracted agencies, must follow established standards set by the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.  

On July 1, 2019, California Assembly Bill 434 (AB 434) was issued, requiring all state agencies and entities to ensure that their websites comply with WCAG standards.  On April 24, 2024, the Los Angeles County, Chief Information Officer issued a Directive requiring all County Departments to comply with this ruling.  Effective June 24, 2024, the United States, Department of Justice (DOJ) published the Final Rule of Nondiscrimination on the Basis of Disability: Accessibility of Web Information and Services of State and Local Government Entities.  This ruling establishes website accessibility standards required by state and local governments under Title II of the Americans with Disabilities Act (ADA).  The DOJ requires that all websites and mobile applications are fully compliant with WCAG 2.1 by April 2026.

WCAG 2.1, Level AA conformance requires websites to meet the following four principles: Perceivable, Operable, Understandable, Robust (POUR):

Web Content Accessibility Level AA

Perceivable

• Provide text alternatives for non-text content.
• Provide captions and other alternatives for multimedia.
• Create content that can be presented in different ways, including by assistive technologies, without losing meaning; and
• Make it easier for users to see and hear content. 

Example:  All posted images, except decorative images, must have alternative text provided to ensure visually impaired individuals can differentiate the image from text, as well as be able to understand content when navigating the page.
 
Operable

• Make all functionality available from a keyboard as well as enable users to utilize different modalities to input information.
• Give users enough time to read and use content.
• Eliminate visual content that may cause seizures or physical reactions (high flashing colors, rapid images, etc.); and
• Help users navigate, find content, and determine where they are on the web page. 

Example:  Ensuring that users who require a screen reader can follow the correct navigation sequence when using the tab feature on a keyboard by ensuring bullets are properly listed on a web page.  Users who require a screen reader to “read” a web page would lose the right order if bullets and/or tags are not in the correct order. 
 
Understandable

• Make text readable and understandable.
• Make content appear and operate in predictable ways; and
• Help users avoid and correct mistakes.

Example:  When creating pages, using high contrast colors on text avoids it being indistinguishable from the background.  Avoid flashing images so that those images will not induce potential seizures in individuals who are sensitive to flashing light.    
 
Robust

Produce web content that is compatible with different browsers, assistive technologies, and other means of accessing web content, so that as technology and user agents evolve, the content will remain accessible. 

Example:  Ensuring web content and code is well-formed, using clear descriptive text for links, and testing web content on various platforms, browsers, and assistive technologies to ensure compatibility.