Accessibility Fundamentals

It is important for everyone to be familiar with fundamental accessibility guidelines and core principals. Everyone should follow practical steps to ensure resources are accessible. Advance technical skills are not required, only a different way of thinking to better plan for accessibility. 

The following principals align to the success criteria of the Web Content Accessibility Guidelines 2.0 Level AA (WCAG 2.0 AA) to support applications, websites, and digital content to be perceivable, operable, understandable, and robust.

All visual elements that convey information must have meaningful alternative text. Alt text is the text equivalent for describing images.

  • Add alt text to pictures, charts, and other visual objects that convey information.
  • Don’t include "image of“, "picture of“, or “logo of” as part of the alt text.
  • Alt text should describe the image in the context of the content.
  • Keep alt text short and concise; limit alt text to 100 characters or less.
  • Decorative images need to be ignored by screen readers. For documents, mark decorative images as "Decorative" or tag them as "Background". For the web, use a null alt attribute (alt=" "). 

More Alt Text Resources:

 

Color plays an important part in accessibility. Keep in mind that some colors will not be apparent for color blind or low vision users. Screen readers can't distinguish color so when it comes to accessibility there are two main things to focus on:

Provide strong color contrast:

  • Text colors on background colors need sufficient color contrast between them.
  • WCAG 2.0 level AA requires a contrast ratio of at least 4.5:1 for normal text.
  • Color contrast checker tools can compare two colors and report on the contrast ratio between them.

Avoid using color alone:

  • Don't convey, compare, or describe information solely on color.
  • Ensure the information is also available in text.
  • Unfortunately, there are no automated tools to ensure that color is not the sole means of communication. 

Headings add structure to digital content which improves scannability and navigation for all users. With headings users and screen readers can skim and browse to specific information on lengthy content.

  • Use paragraph styles (for documents) or heading tags (for web pages) to create headings.
  • Heading 1 (H1) should only be used once. It is reserved for the main title of webpages and documents. 
  • Structure your document using paragraph styles (for documents) or heading tags (for web pages).
  • Don’t use headings to style text.
  • Headings Heading Hierarchy

 

Heading 1 (H1) only used for titles.

Heading 2 (H2) are main sections.
Many can be used though out the content.

Heading 3 are sub sections in H2 sections.

Typically, H3 is the lowest level used
on digital content, but headings can 
reach heading 6 (H6). 

Example of Heading Structure

  • H1 (main title): Using Proper Headings
    • H2: What are Headings
    • H2: Importance of Headings 
    • H2: Heading Hierarchy
      • H3: Level Order 
        • H4: Benefits
          • H5: Quick Navigation
          • H5: Better Organization
    • H2: Headings in Documents
    • H2: Additional Information

Links need to be descriptive and meaningful. They need to clearly describe where they go or what they do. 

  • Write links that make sense when read out of context.
  • Never use Here, Click Here, or More as links.
  • Sometimes phrases could provide a better description than single words.
  • Preserve the link appearance - underlined links help users differentiate them from text.
  • Keep your hyperlink on one line of a paragraph.
  • Making links meaningful might require to re-writing sentences for readability. 
  • Embed the links on digital content instead of using URLS: http://tea.texas.gov/a-f
     

Unclear Link Examples

  • To register for TEA webinars click here
  • Learn color contrast standards here.
  • Accessibility calendar events (More).
  • Accessibility Training (Info)  

Tables are a great way to organize and show relationships between information. Accessible tables start by being simple, rather than complex with many merged cells. Keeping tables simple will help screen reader read the information contained in the table correctly and avoid accessibility barriers. Applying visual cues to a table does not make the table accessible for screen reader users.

  • Tables are for data only and to be used for layout of content.
  • Apply table headers. Use the first, top row as the header row. 
  • Use correct reading order - table data needs to read from left to right, top to bottom.
  • Use simple tables - avoid complex tables layouts and tables nested inside tables.

Understanding WCAG — Info and Relationships (WAI)

Readable content is accessible content. Although text is considered to be accessible the way it is, there could be some constraints.  because it can affect users with dyslexia, cognitive disabilities, who use assistive technologies. 

  • Use proper font sizes - Normal text can be between 11pts - 14pts and headings can be slightly larger.
  • Use normal text spacing.
  • Left align all content. 
  • Use plan language for better readability.
  • Font colors need enough contrast against background colors. 
  • Add a title to your content. It should be the first content read by screen readers or seen by visual users. 
  • Don't use symbols or numbers to create lists. Create ordered and unordered lists. 

Ordered Lists 

  1. Ordered lists uses numbers.
  2. They provide information in sequential order. 
  3. They are used to outline steps to a process.

Unordered List Examples

  • Unordered lists use bullets instead of numbers.
  • They don't need to be in sequential order.​
  • It is recommended to alphabetize list items. 

Media like audio and videos enrich the digital experience for many users, but it needs to be accessible. Media needs to comply with WCAG 2.0 Guidelines and Techniques.​ Apply the following practices: 

Audio 

Audio-only media on websites and digital platforms need transcripts. A transcript is the audio content in text which can be in simple text file (.txt) formats and linked next to the audio files. They should be descriptive as possible to include both audio an d visual information, like someone entering the room. 

Videos

Videos need to have captions that are synchronized with the video's audio dialogue and sounds. Videos that provide visual context will need audio description (AD), an audible narration of the relevant visual information played during natural pauses of the video, that describes what is happening on screen.
 

Also important is to use an accessible media player that supports closed captions, has control buttons that are properly labeled for screen readers, can be operated without a mouse, and works across different browsers and platforms. Media should not autoplay. The users decide when to play the media on digital content.