SchoolAuction.net Accessibility Conformance Report Revised Section 508 Edition

SchoolAuction.net

A web-based software application designed for both the administration and participation in fundraisers, regardless of whether they are in-person, virtual, hybrid, or online. The fundraising process includes:

1. Informing the general public about the fundiser
2. Displaying fundraising items
3. Communication with guests via email and/or SMS
4. Allowing guests to bid or buy items.
5. For registered guests, collection of personal information
6. For buyers, collection of payment information including credit card data
7. For buyers, confirmation and validation of provided data

accessibility@schoolauction.net

• First-pass audit has been completed.
• Basic usability test session completed.
• WCAG Level AAA is not supported, thus this table has been omitted from the report.

Assessment is completed using a combination of manual and automated accessibility testing tools.

Manual tests are completed by working through the W3C Accessibility Assessment Checklist. This list includes items which reflect the latest WCAG standards.

1. Some icons are not visible if the end user customizes their theme.
2. User uploaded images may not contain alternative text descriptions.
3. Some third-party payment provider form controls are not visible when Windows High Contrast theme is in use.
4. Some third-party payment provider images are missing alternative text.

Prerecorded Audio or video content capability is not present.

Prerecorded Video content capability is not present.

Prerecorded Audio content capability is not present.

1. Some informative content is not accessible to assistive technology because of the presence of aria-hidden="true" in the content’s containing tag.
2. Some blocks of regular text are incorrectly marked up as headings.
3. Some content section are incorrectly described as table elements.
4. List structure may not be conveyed for list style content.
5. Current/active state of selected content may not be conveyed.
6. Some third-party payment provider form controls may not convey a disabled state.

The site content is presented in a meaningful sequence

Content and interactions do not rely solely on sensory characteristics.

Third-party payment provider imagery may not be visible in Windows high contrast mode.

The site does not contain audio that plays automatically.

Most site functionality can be accessed and operated using a keyboard.

1. The tab order on some forms is not sequential
2. Tooltips not keyboard accessible.

The site does not include keyboard traps.

Timeout content capability is not present other than when bidding on items, which is allowed under the "Real-time Exception"

The Virtual Auction and Item pages are automically updated as bids are placed.

The site does not contain flashing content.

Currently we do not have a “Skip to content” at the beginning of each page.

Some pages lack unique or descriptive page titles.

1. On Mobile, content which appears under the “Show order summary” control appear visually next to the control, yet is actually placed at the bottom of the page within the DOM.
2. “Previous” and “Next” controls are in reverse DOM order than visual order.
3. Interstitial loading screen message content does not receive focus to convey status.

The purpose of each link in the site can be determined from the link text alone or from the context of the link.

1. Some third-party payment provider controls may be unclear in their purpose.
2. Some form controls are in a different visual order than they are in the DOM.

The default language of the site’s webpage is identified using the lang attribute in the html element.

The site’s components do not initiate a change of context when focused.

On a few forms, if content is recognized, other form elements are shown or hidden.

Where errors are automatically detected, the error is identified, and an error message is provided as text.

1. A few form fields are missing labels.
2. Some third-party payment provider tooltip components may not convey content to assistive technology.

Markup has been tested as valid HTML.

Some user interface components in the site do not provide programmatic name, role, and/or state information.