Skip to main content
CollegeSource Support

Schedule Builder Accessibility Testing Document 4.2.1

 

  1. Evaluation date: 06/26/2015
  2. Evaluation environment:
    1. Testing Staff:
      1. Operating System: Windows 7 Professional 32-bit
      2. Web Browser: Firefox, Chrome, IE
    2. Developer Staff:
      1. Operating System: Mac OS 10.9.5
      2. Web Browsers: Firefox, Chrome, Safari
  3. Evaluation tools:
    1. Testing Staff:
      1. NVDA
      2. Manual keyboard input
      3. Windows High Contrast Mode
      4. Color Changing tools in Firefox
      5. Color Oracle
    2. Developer Staff:
      1. VoiceOver
      2. Manual keyboard input
      3. Mac Accessibility Preferences:
        1. Invert Color
        2. Use Grayscale
      4. Color Changing tools in Firefox
      5. Color Oracle
      6. HTML_CodeSniffer
  4. Test methods:
    1. Manual Testing:
    2. Visual Verification
    3. Screen Reader Verification
    4. Keyboard Accessibility testing
  5. Test results:
    1194.21   Software applications and operating systems. 
    Criteria Test Results
    (a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.
    • Avoid the sole use of device-dependent event handlers
    • Avoid the sole use of the title attribute on elements
    • Ensure all active elements receive keyboard focus
    • Ensure all read-only edit elements can receive keyboard focus
    • Ensure JavaScript functionality is accessible from the keyboard
    • Ensure keyboard focus is not provided to inactive elements
    • Ensure keyboard focus is not trapped
    • Ensure the focus order of interactive elements on the page is logical

     

    (b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards.  Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer.
    • Ensure ARIA roles, states, and properties are valid
    • Avoid inappropriate use of ARIA roles, states, and properties
    (c) A well-defined on-screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes.  The focus shall be programmatically exposed so that assistive technology can track focus and focus changes.
    • Avoid using event handlers that trigger focus changes 
    • Ensure interactive elements can be visually distinguished from non-actionable ones
    • Ensure keyboard focus is indicated visually
      • We have added specific :focus CSS styling within all of our web apps. Schools can customize this to modify this styling to their liking.
    (d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to assistive technology.  When an image represents a program element, the information conveyed by the image must also be available in text.
    • Provide valid labels for form fields
    • Ensure table headers are used in a valid fashion
    • Provide alternative text for images
    • Ensure CSS background images that convey meaning have textual and visible equivalents
    • Ensure image buttons provide alternative text
    • Ensure images provide informative alternative text
    • Ensure link text is meaningful within context
    (e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application’s performance.
    • Ensure that elements with the same functionality are consistently identified across pages
    (f) Textual information shall be provided through operating system functions for displaying text.  The minimum information that shall be made available is text content, text input caret location, and text attributes.
    • Ensure pages that provide alternatives for non-accessible pages provide equivalent functionality
    (g) Applications shall not override user selected contrast and color selections and other individual display attributes.
    • Ensure that user selected contrast and color selections are not overridden by the web applications
    (h) When animation is displayed, the information shall be displayable in at least one non-animated presentation mode at the option of the user.
    • Ensure screen transition animation settles within 5 seconds
    (i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.
    • Ensure color is not the sole means of communicating information
    • Ensure color is not used as the sole method of indicating selection
    • Ensure content with color conveys the same meaning without color, directly in the content, on-screen, and without additional user interaction
    (j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided.
    • Ensure text and images of text provide sufficient contrast
    • Ensure sufficient contrast is provided when background images are not available.
    • Ensure text and images of text provide sufficient color contrast when CSS is disabled.
    • Ensure link text provides sufficient contrast
    (k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz.
    • Ensure blinking or flashing elements are avoided
    • Ensure the blink element is avoided
    (l) When electronic forms are used, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
    • Provide valid labels for form fields
    • Provide valid, concise, and meaningful alternative text for image buttons
    • Ensure form fields are laid out in an intuitive order
    • Ensure form field labels are unique
    • Provide labels or instructions for user input
    1194.22   Web-based intranet and internet information and applications.
    Criteria Supporting Features
    (a) A text equivalent for every non-text element shall be provided (e.g., via “alt”, “longdesc”, or in element content).
    • Provide alternative text for images
    • Ensure images provide informative alternative text
    • Provide valid, concise, and meaningful alternative text for image buttons
    • Ensure page tabs contain proper textual descriptions indicating state and role
    • Ensure charts and graphs provide an informative and visible alternative description
    • Ensure instructions do not rely solely on sensory characteristics
    • Provide text equivalents for icon fonts
    • Provide accessible names for progress bars and meters
    (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
    • Avoid use of multimedia
    (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
    • Ensure color is not the sole means of communicating information
    • Ensure color is not used as the sole method of indicating selection
    • Ensure page tabs contain proper textual descriptions indicating state and role
    • Ensure content with color conveys the same meaning without color, directly in the content, on-screen, and without additional user interaction
    (d) Documents shall be organized so they are readable without requiring an associated style sheet.
    • Ensure documents are readable without style sheets
    • Ensure CSS background images that convey meaning have textual and visible equivalents
    • Ensure that the reading order of content is logical
    • Ensure the reading order of content and elements are correct when viewed without style sheets
    • Avoid the use of implicit headings
    (e) Redundant text links shall be provided for each active region of a server-side image map.
    • Avoid the use of server-side image maps
    (f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
    • Avoid the use of server-side image maps
    (g) Row and column headers shall be identified for data tables.
    • Ensure table headers are used in a valid fashion
    • Ensure data table headers are properly identified
    • Ensure data tables are formatted using table elements
    • Ensure implicit row header cells define scope or use th
    • Ensure data table header elements are provided in the same table as content
    • Ensure table data/headers in separate columns is rendered in separate table cells
    (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.
    • Ensure headers and cells are properly associated
    • Ensure data tables are formatted using table elements
    • Ensure data table header elements are provided in the same table as content
    • Ensure table data/headers in separate columns is rendered in separate table cells
    (i) Frames shall be titled with text that facilitates frame identification and navigation.
    • Avoid use of frames
    (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
    • Avoid blinking or flashing elements
    (k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way.  The content of the text-only page shall be updated whenever the primary page changes.
    • Ensure pages that provide alternatives for non-accessible pages provide equivalent functionality
    (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.
    • Ensure JavaScript functionality is accessible from the keyboard
    • Ensure keyboard and programmatic focus moves to opened menus
    • Ensure keyboard focus returns properly when menus are closed
    • Ensure menus can be opened from the keyboard
    • Ensure sub-menu items are keyboard accessible and contain text equivalents
    • Ensure selectable rows are keyboard accessible
    • Avoid using event handlers that trigger focus changes
    • Avoid forced focus changes that are not user-initiated
    • Ensure that when simulated dialogs are activated focus moves appropriately
    • Ensure keyboard focus returns properly from simulated dialogs
    • Ensure sortable headers can be triggered from the keyboard
    • Provide an accessible alert method for content changes that occur without explicit user knowledge
    (m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).
    • Ensure embedded and linked non-HTML media provide a link to an accessible plug-in
    (n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
    • Provide valid labels for form fields
    • Provide valid, concise, and meaningful alternative text for image buttons
    • Ensure form fields are laid out in an intuitive order
    • Ensure form field labels are unique
    • Provide labels or instructions for user input
    (o) A method shall be provided that permits users to skip repetitive navigation links.
    • Provide a mechanism for skipping past repetitive navigation links
    • Ensure a valid skip link target is present and is located appropriately
    (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
    • Avoid usage of time based sessions and/or timed responses
    1194.31   Functional performance criteria.
    Criteria Supporting Features
    (a) At least one mode of operation and information retrieval that does not require user vision shall be provided, or support for assistive technology used by people who are blind or visually impaired shall be provided.
    • Avoid inappropriate use of ARIA roles, states, and properties
    • Ensure ARIA regions, landmarks and HTML sections are identifiable
    • Ensure ARIA roles, states, and properties are valid
    • Avoid the sole use of device-dependent event handlers
    • Avoid the sole use of the title attribute on elements
    • Ensure all active elements receive keyboard focus
    • Ensure all read-only edit elements can receive keyboard focus
    • Ensure JavaScript functionality is accessible from the keyboard
    • Ensure keyboard focus is not provided to inactive elements
    • Ensure keyboard focus is not trapped
    • Ensure the focus order of interactive elements on the page is logical
    • Provide valid labels for form fields
    • Ensure table headers are used in a valid fashion
    • Provide alternative text for images
    • Ensure CSS background images that convey meaning have textual and visible equivalents
    • Ensure image buttons provide alternative text
    • Ensure images provide informative alternative text
    • Ensure link text is meaningful within context
    (b) At least one mode of operation and information retrieval that does not require visual acuity greater than 20/70 shall be provided in audio and enlarged print output working together or independently, or support for assistive technology used by people who are visually impaired shall be provided.
    • Avoid inappropriate use of ARIA roles, states, and properties
    • Ensure ARIA regions, landmarks and HTML sections are identifiable
    • Ensure ARIA roles, states, and properties are valid
    • Avoid the sole use of device-dependent event handlers
    • Avoid the sole use of the title attribute on elements
    • Ensure all active elements receive keyboard focus
    • Ensure all read-only edit elements can receive keyboard focus
    • Ensure JavaScript functionality is accessible from the keyboard
    • Ensure keyboard focus is not provided to inactive elements
    • Ensure keyboard focus is not trapped
    • Ensure the focus order of interactive elements on the page is logical
    • Provide valid labels for form fields
    • Ensure table headers are used in a valid fashion
    • Provide alternative text for images
    • Ensure CSS background images that convey meaning have textual and visible equivalents
    • Ensure image buttons provide alternative text
    • Ensure images provide informative alternative text
    • Ensure link text is meaningful within context
    (c) At least one mode of operation and information retrieval that does not require user hearing shall be provided, or support for assistive technology used by people who are deaf or hard of hearing shall be provided.
    • Avoid use of audio multimedia and/or audio cues/controls
    (d) Where audio information is important for the use of a product, at least one mode of operation and information retrieval shall be provided in an enhanced auditory fashion, or support for assistive hearing devices shall be provided.
    • Avoid use of audio multimedia and/or audio cues/controls
    (e) At least one mode of operation and information retrieval that does not require user speech shall be provided, or support for assistive technology used by people with disabilities shall be provided.
    • Avoid using speech as the only means to access content
    (f) At least one mode of operation and information retrieval that does not require fine motor control or simultaneous actions and that is operable with limited reach and strength shall be provided.
    • Avoid the sole use of device-dependent event handlers
    • Avoid the sole use of the title attribute on elements
    • Ensure all active elements receive keyboard focus
    • Ensure all read-only edit elements can receive keyboard focus
    • Ensure JavaScript functionality is accessible from the keyboard
    • Ensure keyboard focus is not provided to inactive elements
    • Ensure keyboard focus is not trapped
    • Ensure the focus order of interactive elements on the page is logical
    1194.41   Information, documentation, and support.
    Criteria Supporting Features
    (a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge.
    • Ensure all documentation is made available in an accessible format
    • Ensure a contact in place to receive requests for accessible user documentation
    (b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge.
    • Provide an accessibility and compatibility section with feature list in documentation
    (c) Support services for products shall accommodate the communication needs of end-users with disabilities.
    • Provide access to accessible customer support mechanisms
  • Was this article helpful?