WCAG & ADA Compliance

Although fpvcraft.com does not govern in the United States nor target specifically the United States audience, in order to promote equality and to avoid discrimination among visitors to this blog, fpvcraft adheres to making this website https://fpvcraft.com more accessible to everyone. We will try our best possible to be WCAG and ADA Compliance and will comprehend the following guidelines.

Section 1: Alternatives

• Alt text (1.1.1): All images and non-text content needs alt text (there are exceptions) – In every article, there would be images and these images will have an alt text to describe the role of the image.
• Video & Audio alternatives (1.2.1): All video-only and audio-only content has a text transcript. Transcripts are clearly labelled and linked below the media. – This strictly applies to internal videos and audios and does not include external embedded players such as the ability to play a YouTube video via a player positioned into a blog post. This will include closed captioning wherever is the case but not always limited to this, depending on the source of the video and if this contains a closed caption fused.
• Closed captioning (1.2.2): All video with sound contains accurate closed captioning, but please refer to the above point 1.2.1
• Audio description (1.2.3): For any video with relevant information not conveyed by audio, add an audio description of information conveyed visually or include a text transcript.
• Live captions (1.2.4): Any more formal, live presentations must have closed captions.
• Audio description (1.2.5): An audio description is optional under 1.2.3 level A but not in 1.2.5 AA.

Section 2: Presentation

• Website structure (1.3.1): Use proper markup techniques to structure your website’s content (e.g. use correct heading tags and HTML for ordered and unordered lists)
• Meaningful order (1.3.2): Present content in a meaningful order and sequence so that it reads properly.
• Sensory characteristics (1.3.3): When providing detailed instructions, make it so they aren’t reliant on a single sensory ability.
• Use of colour (1.4.1): Do not rely on colour alone to convey information.
• Audio control (1.4.2): Any audio must be able to be paused, stopped, or muted.
• Colour contrast (1.4.3): There must be a colour contrast ratio of at least 4.5:1 between all text and background.
• Text resize (1.4.4): Text must be able to be resized up to 200% without negatively affecting the ability to read content or use functions.
• Images of text (1.4.5): Do not use images of text unless necessary (e.g. logo).

Section 3: User Control

• Keyboard only (2.1.1): All content and functions on a website must be accessible by keyboard only (i.e. no mouse).
• No keyboard trap (2.1.2): Keyboard-only users must never get stuck on any part of the website; they must be able to navigate forwards and backwards.
• Adjustable time (2.2.1): If there any time limits on a website, users have the ability to turn it off, adjust it, extend it.
• Pause, stop, hide (2.2.2): If there is content that blinks, scrolls, moves, users must have the ability to pause, stop, or hide it.
• Three flashes or below (2.3.1): Web pages do not contain anything that flashes more than three times in any one second period.
• Skip navigation link (2.4.1): A “Skip to Content” or “Skip Navigation” link allows users to bypass the header / navigation menu and go straight to the main content.

Section 4: Understandable

• Page titles (2.4.2): Each page of a website needs to have a unique and descriptive page title.
• Focus order (2.4.3): Users must be able to navigate through a website in a logical sequential order that preserves meaning.
• Link anchor text (2.4.4): The purpose of each link should be clear based on its anchor text (e.g. don’t use “click here”)
• Multiple ways (2.4.5): There are multiple ways to access different pages/information on a website (e.g. search bar, nav menus, sitemap, breadcrumbs, helpful links after content).
• Descriptive headings and labels (2.4.6): Headings and programmatic labels must be clear and descriptive. They do not need to be lengthy.
• Focus indicator (2.4.7): Any “user interface control” that receives focus from a keyboard user should indicate that focus on the current selected element (e.g. add a visible border around a text link).
• Website language (3.1.1): Set the language for your website.
• Language changes (3.1.2): Indicate any language changes for an entire page or within the content.

Section 5: Predictability

• No focus change (3.2.1): Nothing changes merely because an item receives focus; a user must actively choose to activate an item (e.g. hit enter to submit) before a change takes place.
• No input change (3.2.2): Nothing changes just because the information is inputted into a field (e.g. form doesn’t auto-submit once all fields are filled out).
• Consistent navigation (3.2.3): Keep navigation layout consistent throughout all pages of the website (e.g. same links in the same order).
• Consistent identification (3.2.4): Components that have the same function within a website are identified consistently (but not necessarily identically) (e.g. two checkmarks can indicate two different things as long as their function is different — one indicates “approved” on one page but “included” on another).
• Error identification (3.3.1): Make any form errors easy to identify, understand, and correct.
• Form labels and instructions (3.3.2): Programmatically label all form or input fields so that a user knows what input and what format is expected.
• Error suggestions (3.3.3): If an input error is automatically detected, then suggestions for correcting the error should be provided.
• Error prevention on important forms (3.3.4): For pages that create legal commitments or financial transactions or any other important data submissions, one of the following is true: 1) submissions are reversible, 2) the user has an opportunity to correct errors, and 3) confirmation is available that allows an opportunity to review and correct before submission.
• Parsing (4.1.1): Make sure HTML code is clean and free of errors, particularly missing bracket closes. Also, make sure all HTML elements are properly nested.
• Name, role, value (4.1.2): For all user interface components (including forms, links, components generated by scripts), the name, role, and value should all be able to be programmatically determined; make sure components are compatible with assistive technology.

The above sections and points are only a few we may implement in order to make this website accessible to everyone. For more information, please do not hesitate to contact me/us at connect@fpvcraft.com

Please keep in mind that because this website does not target a US audience nor resides in the United States, this is only a benefit of our website implementing these functions in order to promote equality and make this website accessible to everyone.