Accessibility Statement

Our commitment to accessibility

The Checklist

This list is by no means a com­plete list of require­ments for WCAG, EAA, (Euro­pean Acces­si­bil­i­ty Act 2025, or EN 301 549 com­pli­ance, but it does include the most impor­tant items to make your web­site acces­si­ble to peo­ple with dis­abil­i­ties.

The work of keep­ing a web­site in com­pli­ance is nev­er done. It’s an ongo­ing process through­out the life of the site.It is very easy for a web­site to drift out of com­pli­ance as peo­ple add con­tent, fea­tures get added, and plu­g­ins get updat­ed. New font colours are added that don’t meet the min­i­mum con­trast guide­lines, for exam­ple. Or, some­one adds new images with­out adding alt tags.

Acces­si­bil­i­ty com­pli­ance is not a one-time deal; any updates to the site will be made with acces­si­bil­i­ty in mind.

We do not have con­trol over 3rd par­ty cook­ies and will min­imise their use where pos­si­ble. We will also advo­cate to the com­pa­nies if their plug-ins are not com­pli­ant.

We use Word­Press with Divi as our CSS for styling. Some of the DIVI ARIA attrib­ut­es for but­tons and fields do not pro­vide addi­tion­al descrip­tive labels,

**Note: We are work­ing to rec­ti­fy this, as are the team at Divi and Divi Mod­ules. Divi 5 will be released with updates and I have been assured they are work­ing on acces­si­bil­i­ty. We will keep you updat­ed on our progress. We are 89% com­pli­ant and work­ing on the Divi issue #et_mobile_nav_menu for mobile nav­i­ga­tion.

Please con­tact info@rachelkanedesign.ie with any sug­ges­tions regard­ing improve­ments for a more com­fort­able user jour­ney.

Appearance

Text at least 16 px in size.
Colour con­trast rules are fol­lowed.
States are not com­mu­ni­cat­ed just by colour.

Keyboard Access

All links are key­board-acces­si­ble, how­ev­er we use Divi as a CSS, Cas­cad­ing Style Sheet and links have an Aria role of ‘but­ton’ which can be repet­i­tive.

• All nav­i­ga­tion (menus) are key­board-acces­si­ble
• All dynam­ic ele­ments can be oper­at­ed by key­board
• All oth­er func­tion­al­i­ty is oper­a­ble by key­board, test­ed with MAc voiceover and NVDA.
• All of the above have vis­i­ble focus indi­ca­tor (usu­al­ly an out­line)
• Links<a> tag is used for links
• Links in body are dis­tin­guished from sur­round­ing text
• Link text (or aria-label text) is not descrip­tive and marked as ‘but­ton’
• Links that open a new tab or win­dow have some indi­ca­tion this will hap­pen, such as adding “(opens in a new tab)” to the link text or area-label.

Structure

Head­ings are in sequence H1 to H6

Images

Images have rel­e­vant alt text or cap­tions unless pure­ly cos­met­ic, in which case they are hid­den from screen read­ers.
Images do not have title attrib­ut­es

Videos

Videos with audio need audio con­trols, they are playable on the page and also on youtube.
Video has accu­rate tran­script or cap­tions on YouTube.

Forms

Fields have label tags, not place­hold­ers
Sub­mit but­ton clear­ly states what sub­mit­ting the form does, i.e., “sub­scribe to email list”
Fields are key­board-acces­si­ble

Embeds

YouTube iframes have a title attribute describ­ing the iframe’s pur­pose.