Section 508 Web_Apps_Checklist.xlsx
XLSX spreadsheet 33 KB Posted
- Solicitation number
- 75R60220R00001
About this file
This document provides details on a planned federal contract solicitation to distribute pre-exposure prophylaxis for HIV prevention. The Health Resources and Services Administration intends to issue a full and open solicitation by December 1, 2019 to establish and administer a call center, online portal, and eligibility verification process to provide uninsured patients access to donated PrEP medications. Under the contract, a pharmacy network would be established for distributing 30-day or 60-day supplies of donated PrEP drugs to qualified eligible patients via cards with assigned BIN numbers or vouchers. The contractor would reimburse pharmacies and maintain an enrolled patient database over one base year and four option years. Interested parties should monitor the FedBizOpps website for solicitation and amendment details.
View the file
Other files
Show all 31
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Report Details
| Report Details | |
| Tester Name: | |
| Review Date: | |
| URL: | |
| Contact Name: | |
| Site or App Description: | |
| Test Results: | -- |
| Test Environment | |
| Operating System: | |
| Browser & Browser Version: | |
| Compatibility View | -- |
| For more information about each failure please view the WCAG Guidelines at: |
| http://www.w3.org/WAI/WCAG20/quickref/ |
http://www.w3.org/WAI/WCAG20/quickref/ Results
| Guidelines | ID | Failure Conditions | Test Results | Failure Details (Provide Screen/Location) | |
| 1.1 - Text Alternatives | |||||
| Non-Text Content | 1.1.1.A | All images, form image buttons, and image map hot spots have appropriate, concise alternative text. | -- | ||
| 1.1.1.B | Images that do not convey content, are decorative, or with content that is already conveyed in text are given null alt text (alt="") or implemented as CSS backgrounds. | -- | |||
| 1.1.1.C | Equivalent alternatives to complex images are provided in context or on a separate (linked and/or referenced via longdesc) page. | -- | |||
| 1.1.1.D | Embedded multimedia is identified via accessible text. | -- | |||
| 1.1.1.E | Frames are appropriately titled. | -- | |||
| 1.1.1.F | Content intended to be hidden from all users is also hidden from assistive technology | -- | |||
| 1.1.1.G | CSS background images that convey meaning have textual alternatives | -- | |||
| 1.1.1.H | Animated content has an alternative or is described in text. | ||||
| 1.1.1.I | CAPTCHAs are accessible, in visual and audible formats | ||||
| 1.1.1.J | Textual alternative information is updated when an element's state changes | ||||
| 1.2 - Time-based Media | |||||
| Audio-only and Video-only (Prerecorded) | 1.2.1.A | A descriptive text transcript (including all relevant visual and auditory clues and indicators) is provided for non-live, web-based audio (audio podcasts, MP3 files, etc.). | -- | ||
| 1.2.1.B | A text or audio description is provided for non-live, web-based video-only (e.g., video that has no audio track). | -- | |||
| Captions (Prerecorded) | 1.2.2.A | Synchronized captions are provided for non-live, web-based video (YouTube videos, etc.) | -- | ||
| Audio Description or Media Alternative (Prerecorded) | 1.2.3.A | A descriptive text transcript OR audio description audio track is provided for non-live, web-based video | -- | ||
| Captions (Live) | 1.2.4.A | Synchronized captions are provided for all live multimedia that contains audio (audio-only broadcasts, web casts, video conferences, Flash animations, etc.) | -- | ||
| Audio Description (Prerecorded) | 1.2.5.A | Audio descriptions are provided for all video content. NOTE: Only required if the video conveys content visually that is not available in the default audio track. | -- | ||
| 1.3 - Adaptable | |||||
| Info and Relationships | 1.3.1.A | ||||
| Semantic markup is used appropriately to designate headings (<h1>), lists (<ul>, <ol>, and <dl>), emphasized or special text (<strong>, <code>, <abbr>, <blockquote>, for example), etc. | -- | ||||
| 1.3.1.B | |||||
| Tables are used for tabular data and data is contained in separate data cells. | -- | ||||
| 1.3.1.C | Data table headers are appropriately identified (ex. TH for simple tables and the headers attribute for complex tables) | -- | |||
| 1.3.1.D | Data cells are associated with their headers (ex. scope for simple tables or headers and IDs for complex tables) | -- | |||
| 1.3.1.E | Data table captions and summaries are used where appropriate. | -- | |||
| 1.3.1.F | Layout tables identify their purpose and do not contain structural markup | -- | |||
| 1.3.1.G | Text labels are associated with form input elements. | -- | |||
| 1.3.1.H | Related form elements are grouped with fieldset/legend. | -- | |||
| 1.3.1.I | Elements with multiple labels are provided in a meaningful order | -- | |||
| Meaningful Sequence | 1.3.2.A | The reading and navigation order (determined by code order) is logical and intuitive. | -- | ||
| 1.3.2.B | Meaningful CSS content must be available and in a logical order when viewed without style sheets | -- | |||
| 1.3.2.C | Menus, simulated dialogs, calendar pickers, and dynamic content are rendered inline with the controls that spawns them | -- | |||
| Sensory Characteristics | 1.3.3.A | Instructions do not rely upon shape, size, or visual location (e.g., "Click the square icon to continue" or "Instructions are in the right-hand column"). | -- | ||
| 1.3.3.B | Instructions do not rely upon sound (e.g., "A beeping sound indicates you may continue."). | -- | |||
| 1.4 - Distinguishable | |||||
| Use of Color | 1.4.1.A | Color is not used as the sole method of conveying content or distinguishing visual elements. | -- | ||
| 1.4.1.B | Color alone is not used to distinguish links from surrounding text unless the luminance contrast between the link and the surrounding text is at least 3:1 and an additional differentiation (e.g., it becomes underlined) is provided when the link is hovered over or receives focus. | -- | |||
| 1.4.1.C | Non-text content (ex. images) use patterns to convey the same information as color | -- | |||
| Audio Control | 1.4.2.A | A mechanism is provided to stop, pause, mute, or adjust volume for audio from multimedia or animation that automatically plays in software for more than 3 seconds. | -- | ||
| Contrast (Minimum) | 1.4.3.A | Text and images of text have a contrast ratio of at least 4.5:1. | -- | ||
| Resize Text | 1.4.4.A | The page is readable and functional when the text size is doubled. | -- | ||
| Images of Text | 1.4.5.A | If the same visual presentation can be made using text alone, an image is not used to present that text. | -- | ||
| 2.1 - Keyboard Accessible | |||||
| Keyboard | 2.1.1.A | All page functionality is available using the keyboard, unless the functionality cannot be accomplished in any known way using a keyboard (e.g., free hand drawing). | -- | ||
| 2.1.1.B | Page-specified shortcut keys and accesskeys (accesskey should typically be avoided) do not conflict with existing browser and screen reader shortcuts. | -- | |||
| 2.1.1.C | All functionality of the content is operable without requiring specific timings for individual keystrokes. | -- | |||
| 2.1.1.D | Device-dependent event handlers are avoided. | ||||
| No Keyboard Trap | 2.1.2.A | Keyboard focus is never locked or trapped at one particular page element. The user can navigate to and from all navigable page elements (ex. embedded objects) using only a keyboard. | -- | ||
| 2.2 - Enough Time | |||||
| Timing Adjustable | 2.2.1.A | If a page or application has a time limit, the user is given options to turn off, adjust, or extend that time limit. This is not a requirement for real-time events (e.g., an auction), where the time limit is absolutely required, or if the time limit is longer than 20 hours. | -- | ||
| Pause, Stop, Hide | 2.2.2.A | Automatically moving, blinking, or scrolling content (ex. multimedia, animation, etc.) that lasts longer than 5 seconds can be paused, stopped, or hidden by the user. Moving, blinking, or scrolling can be used to draw attention to or highlight content as long as it lasts less than 5 seconds. | -- | ||
| 2.2.2.B | Automatically updating content (e.g., automatically redirecting or refreshing a page, a news ticker, AJAX updated field, a notification alert, etc.) can be paused, stopped, or hidden by the user or the user can manually control the timing of the updates. | ||||
| 2.3 - Seizures | |||||
| Three Flashes or Below Threshold | 2.3.1.A | No page content flashes more than 3 times per second unless that flashing content is sufficiently small and the flashes are of low contrast and do not contain too much red. (See general flash and red flash thresholds) | -- | ||
| 2.4 - Navigable |
Bypass Blocks
| (2.4.1 Does not apply to software.) | 2.4.1.A | A link is provided to skip navigation and other page elements that are repeated across web pages. | -- | |
| 2.4.1.B | If a page has a proper heading structure, this may be considered a sufficient technique instead of a "Skip to main content" link. | |||
| 2.4.1.C | If a page uses frames and the frames are appropriately titled, this is a sufficient technique for bypassing individual frames. | |||
| Page Titles | 2.4.2.A | The web page has a descriptive and informative page title. | -- | |
| Focus Order | 2.4.3.A | The navigation order of links, form elements, etc. is logical and intuitive. | -- | |
| 2.4.3.B | Keyboard focus moves to and returns from elements appropriately. This includes the opening or appearance and closing of menus, dialogs, calendars, etc. | -- | ||
| Link Purpose (In Context) | 2.4.4.A | The purpose of each link (or form image button or image map hotspot) can be determined from the link text alone, or from the link text and its context (e.g., surrounding paragraph, list item, table cell, or table headers). | -- | |
| 2.4.4.B | Links (or form image buttons) with the same text that go to different locations are readily distinguishable. | -- | ||
| Multiple Ways | ||||
| (2.4.5 Does not apply to software.) | 2.4.5.A | Multiple ways are available to find other web pages on the site - at least two of: a list of related pages, table of contents, site map, site search, or list of all available web pages. | -- | |
| Headings and Labels | 2.4.6.A | Page headings and labels for form and interactive controls are informative. Avoid duplicating heading (e.g., "More Details") or label text (e.g., "First Name") unless the structure provides adequate differentiation between them. | -- | |
| Focus Visible | 2.4.7.A | It is visually apparent which page element has the current keyboard focus (i.e., as you tab through the page, you can see where you are). | -- | |
| 3.1 - Readable | ||||
| Language of Page | 3.1.1.A | The language of the page is identified using the HTML lang attribute (<html lang="en">, for example). | -- | |
| Language of Parts | 3.1.2.A | The language of page content that is in a different language is identified using the lang attribute (e.g., <blockquote lang="es">). | -- | |
| 3.2 - Predictable | ||||
| On Focus | 3.2.1.A | When a page element receives focus, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user. | -- | |
| On Input | 3.2.2.A | When a user inputs information or interacts with a control, it does not result in a substantial change to the page, the spawning of a pop-up window, an additional change of keyboard focus, or any other change that could confuse or disorient the user unless the user is informed of the change ahead of time. | -- | |
| Consistent Navigation | ||||
| (3.2.3 Does not apply to software.) | 3.2.3.A | Navigation links that are repeated on web pages do not change order when navigating through the site. | -- | |
| Consistent Identification | ||||
| (3.2.4 Does not apply to software.) | 3.2.4.A | Elements that have the same functionality across multiple web pages are consistently identified. For example, a search box at the top of the site should always be labeled the same way. | -- | |
| 3.3 - Input Assistance | ||||
| Error Identification | 3.3.1.A | Required form elements or form elements that require a specific format, value, or length provide this information as a text description | -- | |
| 3.3.1.B | If utilized, form validation errors are presented in an efficient, intuitive, and accessible manner. The error is clearly identified, quick access to the problematic element is provided, and user is allowed to easily fix the error and resubmit the form. | -- | ||
| Labels or Instructions | 3.3.2.A | Sufficient labels, cues, and instructions for required interactive elements are provided at the beginning of the form or set of fields via instructions, examples, properly positioned form labels, and/or fieldsets/legends. (Note: Placeholder text should not be used alone to convey label or instruction.) | -- | |
| Error Suggestion | 3.3.3.A | If an input error is detected (via client-side or server-side validation), provide suggestions for fixing the input in a timely and accessible manner. | -- | |
| Error Prevention (Legal, Financial, Data) | 3.3.4.A | If the user can change or delete legal, financial, or test data, the changes/deletions can be reversed, verified, or confirmed. | ||
| 4.1 - Compatible | ||||
| Parsing | 4.1.1.A | Significant HTML/XHTML validation/parsing errors are avoided. Check at http://validator.w3.org/ | ||
| Name, Role, Value | 4.1.2.A | For tree and outline components, custom controls, page tabs, progress bars, form controls, elements with sub-menus, etc., ensure the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. | ||
| Software |
Interoperability with
| Assistive Technology | S02.A | Users have control over platform accessibility features | |
| 502.B | There is no interruption between the application and platform accessibility features. | ||
| S02.C | The content of text objects and text attributes are rendered to the screen and are programmatically determinable. Text objects are also modifable with the use of assistive technology. | ||
| Applications | 503.A | If the application allows the user to customize the font size, color, type or contrast content in the application reamins available and respects the settings. | |
| 503.B | If the application offers an alternative interface, the alternative meets all other respective standards. | ||
| 503.C | If the application contains multimedia, captions controls are provided at the same menu level as volume controls. | ||
| 503.D | If the application contains multimedia, audio description controls are provided at the same menu level as volume controls. | ||
| Authoring Tools | 504.A | Where an application is an authoring tool, it provides the necessary functions to create or edit accessible content in the final format. | |
| 504.B | Where an application is an authoring tool, when content is converted to another format any supported accessibility information is carried to the final format. | ||
| 504.C | Where an application is an authoring tool and a PDF of content can be created, the generated PDF complies with PDF/UA standards. | ||
| 504.D | Where an application is an authoring tool, prompts are provided to ensure accessible content is created. | ||
| 504.E | Where an application is an authoring tool, any available templates within it meet accessibility criteria. |
Delete Row
File details come from the government source that posted it. Updated .