About TEA

It is best to start simple when testing for accessibility. Start with the easiest testing methods like using features and techniques already available to all users. These include using native tools and doing manual checks. Automated testing tools will still need to be used to complete testing.

• Native Tools – use built-in accessibility checkers to help find accessibility issues in documents or other platforms. Acrobat and Microsoft have their own versions available to users when working on their applications. Also, perform easy to do computer functions like using the keyboard “Tab” key to navigate tables, webpages, links, and applications. 
  • W3C Keyboard Accessibility 
  • WebAIM Keyboard Techniques 

• Manual Checking – Doing a thorough review of the content after running the accessibility checkers. The checkers are great to use, but limited on what they can check for so don’t rely solely on the checkers results. Always perform a manual check to review for proper alt text, table headers, headings, descriptive link text, and color. For a more comprehensive check, become knowledge in accessibility fundamentals and use an accessibility checklist.

• Automated Tools - Sometimes automated tools don’t find all errors but should be used to help. Use different tools to test different elements, like a color contrast checker for color issues.
  • Accessibility Evaluation Tools List (W3C) – a list of various accessibility tools suggested by the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI) . 
  • Accessible Name & Description Inspector (ANDI) (DHS) - an inspection tool by DHS for web pages to conformance with the Revised Section 508 Standards. 
  • ARC Toolkit (Paciello Group) – Web pages testing resources. 
  • Colour Contrast Analyser (Paciello Group) – a desktop application to check color contrast for digital content. 
  • Contrast Checker (WebAim) – a web-based color contrast checker that analyzes color contrast ratios. 
  • Contrast Triangle (Chip Cullen) – a web-based color checker to measure the contrast among text, links, and background colors. 
  • JAWS Screen Reader (Freedom Scientific) – a popular screen reader.
  • NVDA Screen Reader (NVDA team) - a free and open-source screen reader for Microsoft Windows. 
  • Siteimprove - an enterprise platform designed with accessibility scanning and optimization capabilities. Siteimprove account holders have access to Siteimprove Academy.
  • Validator (W3C) - validator to check the markup validity of many common Web page formats. 
  • Viewport Resizer – responsive Testing tool to test website responsiveness. 
  • WAVE Web Accessibility Evaluation Tool (WebAim) – identify accessibility errors on webpages.

Acquire valuable accessibility training from credible sources that can help individuals have a positive learning experience.

Accessibility General Guides

• 18F Accessibility Guide - A resource for developing accessible products.
• Section 508 Accessibility Training (GSA) - courses and videos to improve the understanding of accessibility and learn on a variety of different accessibility.
• Siteimprove Academy - Access to training courses from Siteimprove. All account users have access to the Siteimprove academy.
• Web Accessibility in Mind (WebAim) - a wide range of accessibility articles that provide to help all users know more and  

Documents & Content

• Acrobat DC Accessibility (Adobe) - a series of accessibility guides to assist in creating accessible PDF documents.
• Adobe InDesign Accessibility (Adobe) - direct and simple accessibility features to apply for accessibility on InDesign documents.
• Microsoft 365 Accessibility Training (Microsoft) - Support videos on accessibility to make Microsoft Office documents be better for everyone.
• Microsoft MSFTEndable (YouTube) - A Microsoft channel on YouTube with dozens of training videos.
• PlainLanguage.gov - A guide to making copy writing clear and easy to understand.

Media and Videos

• Accessible Media Players (Harvard) - Discover the functionality media players need to support accessibility.
• Captions, Transcripts, Audio Description (WAI) - General information for making audio and video media accessible and when your media needs captions.
• Teams Accessibility (Microsoft) - A guide to making products more accessible for everyone.
• YouTube Accessibility (YouTube) - Manage YouTube accessibility settings.
• Zoom Accessibility (YouTube) - a video from Zoom on YouTube that show how to enable accessibility features.

Web Development

• Accessible Form applications (WebAim) - General information on form accessibility requirements.
• ASP.NET Accessibility (IBM) - Guidelines on how to create accessible ASP.NET applications.
• Drupal Accessibility - Resources for building Drupal websites that can be accessed by all.
• Java Accessibility  (IBM) - Accessibility guidelines from IBM for writing accessible Java applications.
• JavaScript Accessibility (WebAim) - Overview for developers on JavaScript Accessibility.
• USWDS Accessibility - A design system for the federal government.

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:

• WebAim's guide to alternative text
• WCAG Success Criteria 1.1.1 Non-text Content

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: https://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)  

Descriptive Link Examples

• TEA webinar registrations are now open.
• Learn about TEA color contrast standards.
• Check for upcoming accessibility events.
• Accessibility Training Information.

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.