Issues & Controversies Accessibility Roadmap

Follow

Infobase is committed to ensuring that its products and services are accessible to everyone.  As part of this commitment, Infobase has identified the following criteria in Issues & Controversies that do not meet a conformance status of Supports.

Infobase sets a standard/guideline for Level AA compliant with the WCAG 2.0 guidelines, Revised Section 508, and European Standard EN 301 549. Please see the latest VPAT for compliance standards that address the additional WCAG 2.1 criteria.  

 

Criteria

Status

Remarks and Explanations

Expected Resolution Date

1.1.1 Non-text Content (Level A)

Under investigation

Some secondary list pages in the Issues and Videos sections have missing alt-text. 


In addition, SVG icon images throughout the website do not have alternative text.


The goal will be to add alternative text descriptions where needed or hide when an image is decorative. 

Q3 - 2022

1.2.1 Audio-only and Video-only (Prerecorded) (Level A)



Issue will not be fixed

Since audio-only media, such as podcasts, are provided by third-party sites, Issues & Controversies relies on the affiliate to provide transcripts (e.g., NPR.org). In addition, it is therefore not a guarantee there will always be an alternative transcript for third-party audio-only media. Finally, there are no non-live, web-based silent videos or animations (e.g., videos or animations that have no audio track.) in Issues & Controversies

NA

1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)



Issue will not be fixed

All videos have interactive and synchronized text transcripts and captions. Text transcripts are downloadable. Most transcripts will have limited if any, audio descriptions. 

NA

1.3.1 Info and Relationships (Level A)

Under investigation

There are some pages, for example, in Court Cases and Pro/Con articles, that may have some heading levels that get skipped. Still, it does not disrupt the use of assistive technology from accurately navigating the information.


The goal is to ensure, information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text, as per: 

Q3 - 2022

2.1.1 Keyboard (Level A)

Under investigation

The goal is complete access to all webpage elements using the keyboard.


Almost all page functionality within Issues & Controversies is available using the keyboard. 


Current exceptions are:  


  • The search box button icon.
  • “Having trouble logging in?” link – in the Your Profile modal.
  • The keyboard tab focus does not always stay within popup modal dialog windows. 
  • Currently, the keyboard tab focus skips some navigational elements when zoomed in at different zoom percentages. This issue will be prioritized to be fixed in future updates.

Q3 - 2022

2.4.4 Link Purpose (In Context) (Level A)

Under investigation

Some links’ purposes may be ambiguous, such as image links and empty links and buttons within some dropdown menus. 


The goal is to add correct accessible names to the links, buttons, and dropdown menus. Also, consider contextualizing any generic links like Read More, Click Here, Previous, and Back.

Q3 - 2022

3.1.1 Language of Page (Level A)

Under investigation

Future developments will ensure the default language of each page in the platform can be programmatically determined. HTML language attributes <html … lang=”en”>will be present in all pages in future updates.

Q3 - 2022

4.1.1 Parsing (Level A)

Under investigation

Some HTML/XHTML validation/parsing errors do exist when code was checked through a HTML/XHTML validator. Parsing errors, however, do not prevent access to the content and may not be noticeable to a user.  


The goal will be to make sure the HTML and ARIA labels are valid according to current web standards and specifications. 

Q3 – 2022

4.1.2 Name, Role, Value (Level A)

Under investigation

Issues & Controversies uses markup designed to facilitate accessibility by following HTML specifications. Name, role, and value attributes are used extensively throughout the site. When HTML is not sufficient, ARIA techniques are used.


Current examples to check: 


  • For SVG images, there are missing ARIA-label attributes that describe the purpose of the image.
  • Use automated test programs like WAVE or HTML Code Sniffer to see if ARIA is being used correctly.

Q3 - 2022

1.4.4 Resize text (Level AA)

Under investigation

Most text, including captions, can be resized up to 200 percent without loss of content or functionality. However, when zoomed in at 200%, the keyboard misses the tab focus on the Hamburger button (i.e., Expand Sidebar Menu) and Search Box Icon (i.e., Search) buttons.  Other issues include skipping Filter by Type dropdowns. 

Q3 - 2022

0 out of 0 found this helpful