# Accessibility

**Accessibility** in web development means creating a web site that everybody can use regardless of one's hardware, software, or sensory, or physical impairment. It is about building a barrier-less web.

While creating accessible website is a *complex process that includes a content strategy*, **Ileana** theme helps you with being *accessibility ready* out of the box. It complies to [WordPress accessibility requirements](https://make.wordpress.org/themes/handbook/review/accessibility/) and was built to help you create a website that passes [WCAG 2.2 level AA](https://webaim.org/standards/wcag/checklist) requirements.

Among other features the theme itself applies *proper headings structure*, uses *ARIA attributes and landmarks* where needed, adds *informative "read more" links*, makes your website navigation *keyboard accessible*, creates *skip links* for you and provides sufficient *color contrast in default color scheme*.

However, please understand that creating an accessible website is not just about a theme. You need to apply accessibility principles also to your website content and be cautious when using plugins. For further information please read [WordPress documentation about accessibility](https://make.wordpress.org/accessibility/handbook/).

And for even more information about accessibility please check:

* [How to evaluate your website accessibility](https://support.webmandesign.eu/accessibility/)
* [Accessibility explained on Wikipedia](https://en.wikipedia.org/wiki/Accessibility)
* [WordPress.tv videos about accessibility](https://wordpress.tv/tag/accessibility/)
* [Getting started with web accessibility by W3.org](https://www.w3.org/WAI/gettingstarted/Overview.html)
* [WebAIM: Web Accessibility In Mind](https://webaim.org/)

#### Focus on Readability

Content area of this theme was designed carefully to provide **the best reading experience** for your visitors. Maximum line width is set to roughly 70 characters (can be tweaked in theme options). With proper line height and spacing around elements it is easier for visitors to digest your website content.

### Headings Hierarchy

Video: [How to use headings for accessibility and SEO](https://learn.wordpress.org/tutorial/using-headings-for-accessibility-and-seo/)

 Video: [Alternative video about headings hierarchy](https://www.youtube.com/watch?v=_xecSWaqiUw)

To comply with accessibility guidelines, the theme follows this headings structure:

#### Max one `h1` on any given page

Theme outputs only one first-level heading (HTML tag `<h1>`) on each page. This is reserved for a page main title.

{% hint style="info" %}
**Important: Exceptions in templates**

Read more about exception from this rule applied with certain templates. For example, you can remove the `h1` title altogether and create your own custom one in a page content.
{% endhint %}

#### Hierarchy

The theme follows the best practice by hierarchically organizing heading levels, not skipping any of them. For example, `h3` headings can be found only in a section titled with level `h2` (and not `h1`). **You should do the same when building your site content** too.

{% hint style="info" %}
**Tip: Test it out!**

In case you would like to test a page headings hierarchy, there is a great browser extension for this called [**HeadingsMap**](https://github.com/dzc34/headingsMap).
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://nghiaxchis.gitbook.io/ncmaz-blog-magazine-full-site-editing-wordpress/basics/accessibility.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.