Page tab controls need to provide proper textual equivalent and accessibility properties to ensure name, role, and state are communicated. When accessibility properties are not provided, users may not know which page tab is select or that the control is a page tab.

Resolve: 2 Instances

Web content needs to notify assistive technologies that page content has updated when a user action occurs but a page reload does not occur. When content within a page changes without reloading users may not be aware of the changes

Resolve: 1 Instance

The title of a page must provide information specific to the currently viewed page. Assistive technologies utilize the page title to indicate the current page location to users and this content should inform the user of the content to be found (topic) or action to be performed on (purpose of) that page.

Resolve: 12 Instances

When colors are used as the sole method for identifying screen elements, controls, or giving instructions, persons who are blind, color blind, or have low vision may find the web page unusable. This provision requires that some other method of identification, such as on-screen text, be combined with the use of color. Color must not be the sole method of indicating a link within non-linked text.

Resolve: 4 Instances

Use of appropriate dialog markup will allow users of screen reader to know the beginning and ending boundaries of the dialog, allow for an accessible name and description on the dialog, and allow the user to understand the purpose of the dialog's content.

Resolve: 3 Instances

When the before, after pseudo elements are used to display non-decorative content users of assistive technology will likely not have access to this text or image information. Without access to this information the content of the page may be incorrectly interpreted.

Resolve: 1 Instance

All interactive functionality needs to be operable with the keyboard. When interactive elements can not be navigated to or operated with the keyboard users who rely on the keyboard may not be able to perform that function.

Resolve: 3 Instances

When form fields have error messages or specific constraints, such as required state, formatting requirements, or unit requirements, these requirements should be communicated visually to the immediate left/above or right/below the field as well as programmatically associated with the field. Examples of form field constraints include:

• Date Masks (i.e. YYYY/MM/DD)
• Required field indicators
• Text representing a minimum and maximum range of numbers

Resolve: 1 Instance

When layout tables do not explicitly indicate they are solely for presentation purposes, user agents, assistive technology, and automated accessibility testing tools may not understand their layout purpose, and may instead incorrectly treat them as data tables

Resolve: 4 Instances

Explicit heading markup must be used for page headings to convey document structure. Implicit headings are those that use font size, boldface, color, background color, extra spacing (not blank lines) or any of a wide variety of purely visual methods to imply meaning. When heading content is not created with proper markup the meaning conveyed by presentation will be lost when style sheets are turned off

Resolve: 15 Instances

Forms should utilize the fieldset and legend elements to group related form controls. By grouping all of the elements in one category users of assistive technologies can understand the relationship of the elements. 

Resolve: 1 Instance

Whenever lists are utilized in a page, they should incorporate the appropriate markup for lists. Lists which are created using tables, indentation, or with images as bullet points should be avoided. 

Resolve: 7 Instances

Radio buttons are intended to provide an ability to choose one (and only one) item from a group of related options. For this reason, radio buttons must be grouped properly for assistive technology to identify them correctly. To do so, content providers should supply identical values for the name attributes for all options in a radio button group. Further, unrelated radio buttons (that is, radio buttons which are not part of the same group) should not have the same value within name attributes.

Resolve: 1 Instance

When ARIA attributes (state, roles, and properties) are inappropriately used, assistive technology may not function as expected. Role and properties are covenants between assistive technology and the application and must be accurate for the intended purpose.

Resolve: 2 Instances

Often CSS, JavaScript, and other DHTML techniques are used to hide or collapse content that is on-screen. This content can also be content that is meant to be dynamically available or hidden based on selected options. This content can sometimes be a small piece of text, a set of links, or another webpage. Assistive technology such as screen readers may render this content to the user if the content is not marked in a certain manner as "hidden"

Resolve: 2 Instances

Data tables must identify text for header cells that label the data cells in the same column or row to identify the purpose of the column to people who can not see the implied visual relationship.

Resolve: 4 Instances

A placeholder attribute should not be used as a label. The placeholder is a short hint intended to aid the user with data entry. The placeholder may not be available to assistive technology and thus may not be relied upon to convey an accessible name or description

Resolve: 6 Instances

Absolute sizing dimensions should not be utilized to specify font size. When absolute font sizes are used, users may not be able to increase or decrease the size of the font or the font may become unreadable or overlap other content.

Resolve: 13 Instances

Text and other content on a page should reflow without requiring scrolling in two dimensions when the horizontal width is 320 CSS pixels/vertical height is 256 CSS pixels. The reflow must not cause loss of content or functionality, although content and functionality may be presented in different ways, such as via a pop-up menu rather than a navigation bar. Users with low vision use the browser zoom function to increase the size of content. When zoom causes the page to require scrolling in multiple directions, a much greater effort is required to read the content.

Resolve: 13 Instances

The heading level of an element needs to match the level communicated visually by the heading on the page. Headings are used to communicate structure, relationship of sections, and describe the purpose of content. For example, in HTML, h2 elements should generally follow h1 elements, h3 elements should follow h2 elements, etc. Content authors should generally not "skip" levels (e.g. h1 directly to h3). When levels are skipped users of assistive technology may not understand the relationship of content.

Resolve: 3 Instances

When ARIA regions, landmarks or HTML5 section elements are provided, users must be able to distinguish them from other regions, landmarks or sections in the page, particularly when two or more instances of the same type are used. When such an element does not provide a descriptive label to clearly identify itself, users of screen readers may have trouble locating the correct section or understanding its purpose.

Resolve: 12 Instances

When new status content is added to the screen without changing the user's context, users should be made aware of the important changes in content that are not given focus in a way that doesn't unnecessarily interrupt their work.

Resolve: 11 instances

Icon fonts are symbols that are implemented by applying a font declaration on a particular character code. These fonts may be text of an HTML element or applied via the before or after pseudo CSS classes. When used inline the font character will likely be announced to users of screen readers as the wrong character. Similarly, even if a standard symbol is indicated -- screen readers will likely not know how to pronounce the symbol. 

Resolve: 20 instances

SD-49822