The Web Backend and Software Development content type is specific to website developers who are writing code or modifying the underlying template of a platform. This includes page templates for the SUNY Oswego website or Lakerlife. All interactive content must be usable regardless of input type (voice, mouse, keyboard, etc.) or display type (mobile, braille display, screen reader, etc.).
The Five Principles
- Identify Content Types: Headings, Paragraphs, Bullets (lists), Hyperlinks, Labels, identify roles (i.e. status messages)
- Provide Text Equivalents: Provide Alt text. Do not use images of text. Make sure linked audio/video have captions, transcripts, and visual description.
- Use Color Carefully: Contrast, Sensory Characteristics
- Provide Descriptive Hyperlinks: Link purpose and location
- Use Clear Language: Overview, Clear labels and instructions; input purpose
Additional Considerations
- Provide Consistent Structure: provide a document title
- Identify the Language: Set this for the document and any sections that are different from the primary language of the document
- Provide ways to navigate that work for all input types: Consistent Navigation, provide multiple ways to navigate the site, Navigable by keyboards and AT, Bypass block, Interactive state changes are visible, Minimum Target size, change of context only by user request, interactions with animations can be disabled, minimize redundant input entry
- Provide error identification, prevention and handling: identify required fields, identify why a form or survey cannot be submitted, identify any specific requirements for input content to be acceptable. Ensure there is always consistent help available.
- Plan for responsive design: Do not lock orientation, does not lose functionality or require scrolling in 2 dimensions at small sizes (320px wide for a vertical scrolling site or 256px high for a horizontal site), text can be scaled 200%
- Typography: Minimum font size 12pt or 16px; do not use all caps; left align text when possible; use space between paragraphs
- Security: A cognitive function test is not required for authentication unless an alternative is available, (AAA) Data and progress does not get lost when a user needs to re-authenticate
- Verify Accessibility: Use a browser accessibility checker. Ideally, verify usability with a screen reader.