Our commitment to accessibility
At Lenox Park Solutions, we believe in the democratization of access.
To ensure that all users come to our platforms as equals, we strive to ensure our products are designed and developed for web accessibility.
Accessibility is an ongoing effort. Our team places great importance on continuous assessment and we acknowledge some items may be missed in our process. If you have encountered an accessibility issue on RoundTables, please contact us.
What we’re doing
-
Accessibility is continuously monitored through design, development, and release cycles.
-
Product standards and documentation are based on Web Content Accessibility Guidelines (WCAG).
-
Manual and automated accessibility checks are ran prior to product and/or feature release.
-
Existing products and features are evaluated to identify accessibility enhancements for users with changing abilities or situational limitations, visible, invisible, and/or temporary disabilities.
Accessibility Principles
When approaching accessibility, we observe the principles set forth within the WCAG framework. These principles are perceivability, operability, understandability, and robustness.
| Perceivability | Can everyone perceive this? |
| Provide text alternatives for non-text content | |
| Provide captions and other alternatives for multimedia | |
| Create content that can be interpreted by assistive technologies without loosing meaning | |
| Make it easier for users to see and hear content | |
| Operability | Can everyone operate this? |
| Make all functions operable from a keyboard | |
| Give users enough time to read and use content | |
| Do not use content that cause seizures | |
| Help users navigate and find content | |
| Understandability | Can everyone understand this? |
| Make content readable and understandable | |
| Make content appear and function in a predictable way | |
| Help users avoid and correct mistakes | |
| Robustness | Can all devices use this? |
| Maximize compatibility with current and future user tools |
Our core accessibility checklist
In our goal to adhere to WCAG guidelines, the following core aspects are evaluated, at minimum, during design and development phases prior to release.
|
Adaptability |
Users can zoom in up to 200%, minimum, without losing content or functionality. |
|
Keyboard shortcuts* |
Basic keyboard shortcuts for primary functionality are supported. |
|
*Planned: RoundTables will continue the expansion of standardized keyboard interactions. *Limitations: At this time, some drop-down components allow for the selection of menu items through the use of the Tab key. Date fields do not support the full range of keyboard interactions. |
|
|
Image tagging, text alternatives |
Images are textually tagged or otherwise available to assistive technology. |
|
Image consistency |
Icons and meaning assigned to images is consistent. |
|
Links |
Links indicate their purpose, in context. |
|
Animations |
Loading animation is included, but is not used in conjunction with basic functionality. |
|
Flashing and blinking |
Features do not flash or blink greater than 2 Hz or lower than 55Hz. |
|
Application plug-ins |
No additional plug-ins are necessary to view or interact with content. |
|
Time limits |
Feature or item of functionality is not limited by time. If a time limitation is necessary, it is extendable. |
|
Text contrast |
Enough contrast is provided between text and its background so that it can be read by people with moderately low vision |
|
Link Contrast |
Links are differentiated from the rest of the content, either with an underline, or with a color that must have at least 3:1 contrast with surrounding body text. |
|
Text feedback |
Links present a non-color indicator on mouse hover and keyboard focus. |
|
Interface contrast |
User interface components adhere to a minimum contrast ratio of 3.1 |
|
Text size |
Body text line height is at least 1.5x the font size |
|
Text positioning |
Blocks of text aren’t justified (aligned to both the left and the right margins). |
|
Text size |
Body text is 16px at a minimum. |
|
Text line length |
Body text line length is 50-60 characters per line on desktop and 30-40 on mobile. |
|
Element feedback |
Interactive elements have hover states. |
|
Element feedback |
Interactive elements have touch states. |
|
Element feedback |
Interactive elements have focus states. |
|
Element feedback |
Interactive elements have active states. |
|
Element feedback |
Interactive elements have disabled states. |
|
Element feedback |
Interactive elements have loading states. |
|
Touch targets |
Touch targets meet a minimum of 24x24 pixels. |
|
Input label visibility |
Form input labels are visible at all times. |
|
Icon labels |
Icons are always paired with text. |
|
Icon placement |
Icons are used to make content more easily scannable. |
|
Meaning cues |
Information isn’t conveyed by color alone. |
|
Descriptive labels |
Buttons and form fields have descriptive labels. |
|
Form feedback |
Required and invalid form fields are clearly communicated. |
Comments
0 comments
Please sign in to leave a comment.