Site Report
This tab shows accessibility issues, indicating problems for older users, people with disabilities or accessibility needs. Automated testing cannot detect all accessibility issues, so should be used alongside human testing.
| Level | WCAG 2.1 | Section 508 - 2017 | Key |
|---|
| A |  | | Pages with level A issues are unusable for some people |
|---|
| AA |  | | Pages with level AA issues are very difficult to use |
|---|
| AAA |  | | Pages with level AAA issues can be difficult to use |
|---|
| Priority | Description and URL | Guideline and Line# | Count |
|---|
Level A
7 issues on 1 pages | |
| | alt text should not contain placeholders like 'picture' or 'spacer'. | WCAG 2.1 A F30 Section 508 (2017) A F30 | 1 pages |
|
For purely decorative images and spacers use alt='', for images of text use the text, and for other images use a description of the image. Impact on users: - JAWS : Reads out placeholder text, instead of a useful image description.
- NVDA : Reads out placeholder text, instead of a useful image description.
- VoiceOver : Reads out placeholder text, instead of a useful image description.
| 1.1.1 1.2.1 | |
| alt='en_US'
https://www.tantrafuengirola.com/ | Line 1986 | |
| | Each a element must contain text or an img with an alt attribute. | WCAG 2.1 A F89 Section 508 (2017) A F89 | 1 pages |
|
A link name allows screen readers to voice what the links does. If there is no link text / `alt` text, or the text / image is hidden by CSS, screen readers have nothing to read, so read out the URL instead. To add a name do one of the following:
- Add text between the
a element start and end tags
- Add an
aria-label attribute
- Add an
aria-labelledby attribute
- Add a descriptive
img alt attribute if the link contains an img element
img elements with role=presentation or role=none are not included in the link's accessible name. | 2.4.4 2.4.9 4.1.2 | |
| https://www.tantrafuengirola.com/ | Line 1017 1222 1703 1779 1985
...
| |
| | HTML form control has no accessible name. | WCAG 2.1 A F68 Section 508 (2017) A F68 | 1 pages |
|
A label (or name) linked to the control allows screen readers to voice the label correctly when reading the control. To add a label do one of the following:
- Use a
label element with the for attribute set to the ID of the form control
- Wrap a
label element around the form control
- Add a
title attribute
- Add an
aria-label attribute
- Add an
aria-labelledby attribute
| 4.1.2 | |
| https://www.tantrafuengirola.com/ | Line 1916 | |
| | iframe and frame elements must have a title attribute. | WCAG 2.1 A 4.1.2 Section 508 (2017) A 4.1.2 | 1 pages |
|
Add a title attribute or ARIA label to each iframe and frame element (e.g. title='Main Content'). Without a title some screen readers read out the frame filename, which is usually meaningless. Impact on users: - VoiceOver macOS 12.5 Safari 15.6 macOS 12.5.1 Reading: Meaningless frame title read out.
- VoiceOver macOS 11.5 Safari 15.0 macOS 11.5.2 Reading: Meaningless frame title read out.
- VoiceOver macOS 10.15 Safari 14.1 macOS 10.15.7 Reading: Meaningless frame title read out.
- VoiceOver macOS 10.14 Safari 13.0 macOS 10.14.6 Reading: Meaningless frame title read out.
| | |
| https://www.tantrafuengirola.com/ | Line 1956 | |
| | img elements must have an accessible name. | WCAG 2.1 A F65 Section 508 (2017) A F65 | 1 pages |
|
Add an alt attribute describing the image, which screen readers voice instead of the image.
Spacer images and purely decorative images should use alt="".
Do not use alt text containing only spaces since that's voiced as an unlabeled image. Impact on users: - NVDA 2022.2 Chrome 105 Windows 10 Reading: Image ignored.
- NVDA 2022.2 FF102 Windows 10 Reading: Image ignored.
- NVDA 2022.2 Edge 105 Windows 10 Reading: Image ignored.
- NVDA 2021.2 Chrome 94 Windows 10 Reading: Image ignored.
- NVDA 2021.2 FF91 Windows 10 Reading: Image ignored.
- NVDA 2021.2 Edge 94 Windows 10 Reading: Image ignored.
- NVDA 2020.2 Chrome 86 Windows 10 Reading: Image ignored.
- NVDA 2020.2 FF78 Windows 10 Reading: Image ignored.
- NVDA 2020.2 Edge 92 Windows 10 Reading: Image ignored.
- NVDA 2019.2 Chrome 79 Windows 10 Reading: Image unlabeled.
- NVDA 2019.2 FF68 Windows 10 Reading: Image ignored.
- JAWS 2022.2207.25 Chrome 105 Windows 10 Reading: Image ignored.
- JAWS 2022.2207.25 FF102 Windows 10 Reading: Image ignored.
- JAWS 2022.2207.25 Edge 105 Windows 10 Reading: Image ignored.
- JAWS 2021.2107.12 Chrome 94 Windows 10 Reading: Image ignored.
- JAWS 2021.2107.12 FF91 Windows 10 Reading: Image ignored.
- JAWS 2021.2107.12 Edge 94 Windows 10 Reading: Image ignored.
- JAWS 2020.2008.24 Chrome 86 Windows 10 Reading: Image ignored.
- JAWS 2020.2008.24 FF78 Windows 10 Reading: Image ignored.
- JAWS 2020.2008.24 Edge 92 Windows 10 Reading: Image ignored.
- JAWS 2019.1912.1 Chrome 79 Windows 10 Reading: Image unlabeled.
- JAWS 2019.1912.1 FF68 Windows 10 Reading: Image ignored.
- VoiceOver macOS 12.5 Safari 15.6 macOS 12.5.1 Reading: Image filename read out.
- VoiceOver macOS 11.5 Safari 15.0 macOS 11.5.2 Reading: Image filename read out.
- VoiceOver macOS 10.15 Safari 14.1 macOS 10.15.7 Reading: Image filename read out.
- VoiceOver macOS 10.14 Safari 13.0 macOS 10.14.6 Reading: Image filename read out.
- VoiceOver iOS 15.6 Safari iOS 15.6 iOS 15.6 Touch: Image filename read out.
- VoiceOver iOS 14.7 Safari iOS 14.7 iOS 14.7 Touch: Image filename read out.
- VoiceOver iOS 13.3 Safari iOS 13.3 iOS 13.3 Touch: Image filename read out.
- VoiceOver iOS 12.4 Safari iOS 12.4 iOS 12.4.1 Touch: Image filename read out.
| 1.1.1 | |
| https://www.tantrafuengirola.com/ | Line 1986 | |
| | Link uses general text like 'Click Here' with no surrounding text explaining link purpose. | WCAG 2.1 A F63 Section 508 (2017) A F63 | 1 pages |
|
Screen reader users use text around links to help understand what the link does.
If the link text is very general, and there's no surrounding text, there's no way to work out what the link does.
Either use a descriptive link label (which helps all users) or add an aria-label or aria-describedby to the link (which helps screen reader users). | 2.4.4 2.4.9 | |
| Link text: click here
https://www.tantrafuengirola.com/ | Line 1670 | |
| | No space between attributes. | HTML5 WCAG 2.1 A 4.1.1 Section 508 (2017) A 4.1.1 | 1 pages |
|
| | |
| https://www.tantrafuengirola.com/ | Line 3366 | |
Level AA
3 issues on 2 pages | |
| | Ensure that text and background colors have enough contrast. | WCAG 2.1 AA 1.4.3 Section 508 (2017) AA 1.4.3 | 2 pages |
|
Some users find it hard to read light gray text on a white background, dark gray text on a black background and white text on a red background.
- The contrast ratio should be 3.0 or more for 18 point text, or larger
- The contrast ratio should be 3.0 or more for 14 point bold text, or larger
- The contrast ratio should be 4.5 or more for all other text
| 1.4.6 | |
| The text color to background color contrast ratio after composition is:
1.89 with
color: rgb(255,255,255);background-color: rgb(214,185,129);font-size: 9.75pt;font-weight: 600;
1.89 with
color: rgb(255,255,255);background-color: rgb(214,185,129);font-size: 9.75pt;font-weight: 600;
1.89 with
color: rgb(255,255,255);background-color: rgb(214,185,129);font-size: 9.75pt;font-weight: 600;
https://www.tantrafuengirola.com/ | Line 1540 1569 1670 | |
| The text color to background color contrast ratio after composition is:
1.89 with
color: rgb(255,255,255);background-color: rgb(214,185,129);font-size: 12pt;font-weight: 400;
https://www.tantrafuengirola.com/wp-content/themes/aviana/assets/css/modules.min.css?ver=6.1.1 | Line 53 | |
| | Phrases in a different language should be in a span or div with a lang attribute. | WCAG 2.1 AA 3.1.2 Section 508 (2017) AA 3.1.2 | 1 pages |
|
Non-English phrases in English text, or English phrases in non-English text, will be mispronounced by a screen reader unless they are identified with a lang attribute. | | |
| HTML language: lang=en-us lang=en-us lang=en-us lang=en-us
https://www.tantrafuengirola.com/ | Line 1376 1394 1439 1457 | |
| | The CSS outline or border style on this element makes it difficult or impossible to see the dotted link focus outline. | WCAG 2.1 AA F78 Section 508 (2017) AA F78 | 1 pages |
|
Do not remove the default outline style, and change any border styles to avoid obscuring the focus outline around focusable elements.
Using a border or outline style that obscures the focus ring causes problems for keyboard-only users in:
- Chrome (obscures the focus indicator on links, buttons, dropdowns and range controls)
- Firefox (obscures the focus indicator on links)
- Internet Explorer (obscures the focus indicator on links, buttons and range controls)
| 1.4.11 2.4.7 | |
| :focus and :not(:focus) have same outline: :focus and :not(:focus) have same outline: :focus and :not(:focus) have same outline: :focus and :not(:focus) have same outline: :focus and :not(:focus) have same outline:
https://www.tantrafuengirola.com/ | Line 895 910 940 1017 1985
...
| |
Level AAA
3 issues on 1 pages | |
| | Avoid specifying a new window as the target of a link with target=_blank. | WCAG 2.1 AAA F22 | 1 pages |
|
Displaying new windows without warning can be very confusing to non-sighted and mobile users.
Some screen readers and mobile devices give very little indication a new tab or window has opened.
If you cannot avoid displaying a new window, insert an "opens in a new window" warning into the link text
or add the warning to the link using a title attribute or aria-describedby attribute. | 3.2.5 | |
| https://www.tantrafuengirola.com/ | Line 1540 1670 1986 1986 1986
...
| |
| | Don't use CSS animations or transitions in interactions without giving the user a way to turn them off. | WCAG 2.1 2.3.3 | 1 pages |
|
Use the @media (prefers-reduced-motion) media query to respect user preferences. | | |
| :hover transition: all 0.2s :hover transition: all 0.2s :hover transition: all 0.2s :hover transition: all 0.2s
https://www.tantrafuengirola.com/ | Line 1986 1986 1986 1986 | |
| | Link uses general text like 'Click Here' which doesn't explain link purpose. | WCAG 2.1 AAA F84 | 1 pages |
|
Screen reader users often tab from one link to the next, or use the 'Next Link' command.
Moving between links labelled 'click here' sounds like 'Click here, tab, click here, tab, click here'.
Change the link text, or add an aria-label, so the link makes sense when read without the surrounding text. | 2.4.9 | |
| Link text: click here
https://www.tantrafuengirola.com/ | Line 1670 | |
| Expand all 13 issues | | |