Defines | |
| #define | COREDATA_ALLOCATORS_INCLUDE "eod/memoryutils/stdallocator.h" |
| #define | COREDATA_MEMORY_ALLOCATORS(CLASS_TYPE) |
| #define COREDATA_ALLOCATORS_INCLUDE "eod/memoryutils/stdallocator.h" |
Declares the name of the file to include for the memory allocators.
Defining this macro when re-compiling coredata allows the default memory pooling allocators to be replaced with a user defined version.
The file named by this macro should provide definition for the macro COREDATA_MEMORY_ALLOCATORS which needs to define memory management operators. An template would be
#define COREDATA_MEMORY_ALLOCATORS(CLASS_TYPE)\ public:\ void* operator new(size_t size) { return my_scalar_allocator(size); } \ void* operator new [](size_t size) { return my_array_allocator(size); } \ void operator delete(void* p) { my_scalar_delete(p); } \ void operator delete[](void* p) { my_array_delete(p); }
Use the following where no definition is specified
#define COREDATA_MEMORY_ALLOCATORS(CLASS_TYPE)
Definition at line 42 of file stdallocators.h.
| #define COREDATA_MEMORY_ALLOCATORS | ( | CLASS_TYPE | ) |
Defines custom memory allocation member functions.
Add this macro to all non-abstract Serializable classes to provide pooling versions of:
| CLASS_TYPE | The name of the class that this macro is within. |
Definition at line 74 of file stdallocators.h.


A refund.
Public Properties | |
| const | DIR = 'refunds' |
| const | MAP |
| const | REASON_CUSTOMER = 'customer' |
| const | REASON_DAMAGE = 'damage' |
| const | REASON_OTHER = 'other' |
| const | REASON_RESTOCK = 'restock' |
| const | TYPE = 'refund' |
| Public Properties inherited from AbstractEntity | |
| const | DIR = '' |
| All subclasses must redeclare this to match their REST directory (without container). More... | |
| const | TYPE = '' |
| All subclasses must redeclare this to match their types. More... | |
| Public Properties inherited from Data | |
| const | MAP = [] |
| const | PATCH = [] |
Protected Properties | |
| Order | $order |
| Protected Properties inherited from Data | |
| Api | $api |
| Pool | $pool |
Public Methods | |
| __construct (Order $order, array $data=[]) | |
| magic string | getCreatedAt () |
| magic string | getId () |
| magic string | getNote () |
| Order | getOrder () |
| magic Adjustment[] | getOrderAdjustments () |
| magic string | getProcessedAt () |
| magic RefundItem[] | getRefundLineItems () |
| magic Transaction[] | getTransactions () |
| magic string | getUserId () |
| magic bool | hasOrderAdjustments () |
| magic bool | hasRefundLineItems () |
| magic bool | hasTransactions () |
| RefundItem | newItem () |
| Transaction | newTransaction () |
| magic $this | setCurrency (string $currency) |
| magic $this | setDiscrepancyReason (string $reason) |
| $this | setFullShipping () |
| magic $this | setNote (string $note) |
| magic $this | setNotify (bool $notify) |
| magic $this | setProcessedAt (string $iso8601) |
| magic $this | setRefundLineItems (RefundItem[] $items) |
| $this | setShippingAmount (string $amount) |
| magic $this | setTransactions (Transaction[] $transactions) |
| magic $this | setUserId (string $id) |
| Public Methods inherited from AbstractEntity | |
| string | __toString () |
| string[] | getPoolKeys () |
| bool | hasId () |
| $this | reload () |
| Fully reloads the entity from Shopify. More... | |
| Public Methods inherited from Data | |
| mixed | __call (string $method, array $args) |
| __construct ($caller, array $data=[]) | |
| string | serialize () |
| Dehydrated JSON encode. More... | |
| array | toArray () |
| void | unserialize ($serialized) |
| Public Methods inherited from CreateTrait | |
| $this | create () |
Protected Methods | |
| _container () | |
| The container/owner object, if any. More... | |
| Protected Methods inherited from AbstractEntity | |
| mixed | _get (string $field) |
| Lazy-loads missing fields. More... | |
| void | _onDelete () |
| void | _onSave () |
| void | _reload (string $field) |
| Protected Methods inherited from Data | |
| mixed | _hydrate (string $class, $item) |
| A factory that also hydrates / caches entities. More... | |
| array | _select ($subject, callable $filter,... $args) |
Magic method: selectField(callable $filter) More... | |
| $this | _setData (array $data) |
| Clears all diffs and sets all data, hydrating mapped fields. More... | |
| $this | _setField (string $field, $value) |
| Sets a value, hydrating if mapped, and clears the diff. More... | |
| Protected Methods inherited from CreateTrait | |
| string | _dir () |
The POST directory. More... | |
Additional Inherited Members | |
| Public Static Methods inherited from AbstractEntity | |
| static null self | load ($caller, string $id, array $query=[]) |
| static self[] | loadAll ($caller, string $path, array $query=[]) |
| const MAP |
|
protected |
| magic string getCreatedAt | ( | ) |
| magic string getId | ( | ) |
Reimplemented from AbstractEntity.
| magic string getNote | ( | ) |
| magic Adjustment [] getOrderAdjustments | ( | ) |
| magic string getProcessedAt | ( | ) |
| magic RefundItem [] getRefundLineItems | ( | ) |
| magic Transaction [] getTransactions | ( | ) |
| magic string getUserId | ( | ) |
| magic bool hasOrderAdjustments | ( | ) |
| magic bool hasRefundLineItems | ( | ) |
| magic bool hasTransactions | ( | ) |
| RefundItem newItem | ( | ) |
| Transaction newTransaction | ( | ) |
| magic $this setRefundLineItems | ( | RefundItem[] | $items | ) |
| magic $this setTransactions | ( | Transaction[] | $transactions | ) |


© 2007-2018 SIL International
The Syriac (Phonetic layout) keyboard is based on standard Syriac keyboards.
The following fonts are included with this keyboard. These fonts have been provided by Beth Mardutho: The Syriac Institute.
| East Syriac Adiabene | East Syriac Ctesiphon |
| Estrangelo Antioch | Estrangelo Edessa |
| Estrangelo Midyat | Estrangelo Nisibin |
| Estrangelo Quenneshrin | Estrangelo Talada |
| Estrangelo TurAbdin | |
| Serto Batnan | Serto Jerusalem |
| Serto Kharput | Serto Malankara |
| Serto Mardin | Serto Urhoy |
Font license Font documentation


Weather Dashboard
Search for a city name:
Search
Clear history
Search for a city to view the 5-day weather forecast.


---
layout: post
title: no title
date: '2009-11-24T22:47:00+00:00'
tags: []
tumblr_url: http://backlog.robbevan.com/post/256110675/video-of-tiny-tim-performance-mentioned-in
---
Video of Tiny Tim performance mentioned in Pynchon’s Inherent Vice - Boing Boing


1
2
3
2016
Present
Malduino
BADUSB x Arduino Pro Micro
Electronics
Arduino
Programming
Security
View the work
April
2016
AutoGarduino
Highly Efficient automated gardening
Automation
Arduino
Sensors
Sustainable Energy
View the work
2016
Present
Multipurpose Server
Home server for multiple uses
Hardware
Linux
Internet of Things
Hardware components
View the work
2015
Present
Portable Wifi Hacking Arsenal
Raspberry Pi x Alfa AWUS036NHA
Electronics
Raspberry Pi
Raspbian
BLE
Aircrack-ng
View the work
Oct.
2015
QR Attendance Taker
QR Technology x Z-Bar
Automation
QR
Automation
Programming
View the work
April
2016
Bluetooth Terminal Communication
BLE x BLUETERM
Application
Bluetooth
SSH
Terminal
View the work
Jul.
2012
Hack a cheap EC Probe
Make EC probe from recycled material
Electronics
Arduino
View the work


|
| err_t | raw_bind (struct raw_pcb *pcb, const ip_addr_t *ipaddr) |
| |
| void | raw_bind_netif (struct raw_pcb *pcb, const struct netif *netif) |
| |
| err_t | raw_connect (struct raw_pcb *pcb, const ip_addr_t *ipaddr) |
| |
| void | raw_disconnect (struct raw_pcb *pcb) |
| |
| void | raw_recv (struct raw_pcb *pcb, raw_recv_fn recv, void *recv_arg) |
| |
| err_t | raw_sendto (struct raw_pcb *pcb, struct pbuf *p, const ip_addr_t *ipaddr) |
| |
| err_t | raw_sendto_if_src (struct raw_pcb *pcb, struct pbuf *p, const ip_addr_t *dst_ip, struct netif *netif, const ip_addr_t *src_ip) |
| |
| err_t | raw_send (struct raw_pcb *pcb, struct pbuf *p) |
| |
| void | raw_remove (struct raw_pcb *pcb) |
| |
| struct raw_pcb * | raw_new (u8_t proto) |
| |
| struct raw_pcb * | raw_new_ip_type (u8_t type, u8_t proto) |
| |
Implementation of raw protocol PCBs for low-level handling of different types of protocols besides (or overriding) those already available in lwIP.
- See also
- APIs
◆ raw_bind()
Bind a RAW PCB.
- Parameters
-
| pcb | RAW PCB to be bound with a local address ipaddr. |
| ipaddr | local IP address to bind with. Use IP4_ADDR_ANY to bind to all local interfaces. |
- Returns
- lwIP error code.
- ERR_OK. Successful. No error occurred.
- ERR_USE. The specified IP address is already bound to by another RAW PCB.
- See also
- raw_disconnect()
◆ raw_bind_netif()
| void raw_bind_netif |
( |
struct raw_pcb * |
pcb, |
|
|
const struct netif * |
netif |
|
) |
| |
Bind an RAW PCB to a specific netif. After calling this function, all packets received via this PCB are guaranteed to have come in via the specified netif, and all outgoing packets will go out via the specified netif.
- Parameters
-
| pcb | RAW PCB to be bound with netif. |
| netif | netif to bind to. Can be NULL. |
- See also
- raw_disconnect()
◆ raw_connect()
Connect an RAW PCB. This function is required by upper layers of lwip. Using the raw api you could use raw_sendto() instead
This will associate the RAW PCB with the remote address.
- Parameters
-
| pcb | RAW PCB to be connected with remote address ipaddr and port. |
| ipaddr | remote IP address to connect with. |
- Returns
- lwIP error code
- See also
- raw_disconnect() and raw_sendto()
◆ raw_disconnect()
| void raw_disconnect |
( |
struct raw_pcb * |
pcb | ) |
|
Disconnect a RAW PCB.
- Parameters
-
| pcb | the raw pcb to disconnect. |
◆ raw_new()
| struct raw_pcb* raw_new |
( |
u8_t |
proto | ) |
|
Create a RAW PCB.
- Returns
- The RAW PCB which was created. NULL if the PCB data structure could not be allocated.
- Parameters
-
| proto | the protocol number of the IPs payload (e.g. IP_PROTO_ICMP) |
- See also
- raw_remove()
◆ raw_new_ip_type()
| struct raw_pcb* raw_new_ip_type |
( |
u8_t |
type, |
|
|
u8_t |
proto |
|
) |
| |
Create a RAW PCB for specific IP type.
- Returns
- The RAW PCB which was created. NULL if the PCB data structure could not be allocated.
- Parameters
-
| type | IP address type, see lwip_ip_addr_type definitions. If you want to listen to IPv4 and IPv6 (dual-stack) packets, supply IPADDR_TYPE_ANY as argument and bind to IP_ANY_TYPE. |
| proto | the protocol number (next header) of the IPv6 packet payload (e.g. IP6_NEXTH_ICMP6) |
- See also
- raw_remove()
◆ raw_recv()
Set the callback function for received packets that match the raw PCB's protocol and binding.
The callback function MUST either
- eat the packet by calling pbuf_free() and returning non-zero. The packet will not be passed to other raw PCBs or other protocol layers.
- not free the packet, and return zero. The packet will be matched against further PCBs and/or forwarded to another protocol layers.
◆ raw_remove()
| void raw_remove |
( |
struct raw_pcb * |
pcb | ) |
|
Remove an RAW PCB.
- Parameters
-
| pcb | RAW PCB to be removed. The PCB is removed from the list of RAW PCB's and the data structure is freed from memory. |
- See also
- raw_new()
◆ raw_send()
Send the raw IP packet to the address given by raw_connect()
- Parameters
-
| pcb | the raw pcb which to send |
| p | the IP payload to send |
◆ raw_sendto()
Send the raw IP packet to the given address. An IP header will be prepended to the packet, unless the RAW_FLAGS_HDRINCL flag is set on the PCB. In that case, the packet must include an IP header, which will then be sent as is.
- Parameters
-
| pcb | the raw pcb which to send |
| p | the IP payload to send |
| ipaddr | the destination address of the IP packet |
◆ raw_sendto_if_src()
Send the raw IP packet to the given address, using a particular outgoing netif and source IP address. An IP header will be prepended to the packet, unless the RAW_FLAGS_HDRINCL flag is set on the PCB. In that case, the packet must include an IP header, which will then be sent as is.
- Parameters
-
| pcb | RAW PCB used to send the data |
| p | chain of pbufs to be sent |
| dst_ip | destination IP address |
| netif | the netif used for sending |
| src_ip | source IP address |


## pygame - Python Game Library ## Copyright (C) 2008 Marcus von Appen ## ## This library is free software; you can redistribute it and/or ## modify it under the terms of the GNU Library General Public ## License as published by the Free Software Foundation; either ## version 2 of the License, or (at your option) any later version. ## ## This library is distributed in the hope that it will be useful, ## but WITHOUT ANY WARRANTY; without even the implied warranty of ## MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU ## Library General Public License for more details. ## ## You should have received a copy of the GNU Library General Public ## License along with this library; if not, write to the Free ## Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA ## ## Marcus von Appen ##<EMAIL_ADDRESS>"""pygame module for accessing sound sample data Functions to convert between numpy arrays and Sound objects. This module will only be available when pygame can use the external numpy package. Sound data is made of thousands of samples per second, and each sample is the amplitude of the wave at a particular moment in time. For example, in 22-kHz format, element number 5 of the array is the amplitude of the wave after 5/22000 seconds. Each sample is an 8-bit or 16-bit integer, depending on the data format. A stereo sound file has two values per sample, while a mono sound file only has one. Supported array systems are numpy The array type to use can be changed at runtime using the use_arraytype() method, which requires one of the above types as string. Sounds with 16-bit data will be treated as unsigned integers, if the sound sample type requests this. """ import pygame._numpysndarray as numpysnd def array (sound): """pygame.sndarray.array(Sound): return array Copy Sound samples into an array. Creates a new array for the sound data and copies the samples. The array will always be in the format returned from pygame.mixer.get_init(). """ return numpysnd.array (sound) def samples (sound): """pygame.sndarray.samples(Sound): return array Reference Sound samples into an array. Creates a new array that directly references the samples in a Sound object. Modifying the array will change the Sound. The array will always be in the format returned from pygame.mixer.get_init(). """ return numpysnd.samples (sound) def make_sound (array): """pygame.sndarray.make_sound(array): return Sound Convert an array into a Sound object. Create a new playable Sound object from an array. The mixer module must be initialized and the array format must be similar to the mixer audio format. """ return numpysnd.make_sound (array) def use_arraytype (arraytype): """pygame.sndarray.use_arraytype (arraytype): return None DEPRECATED - only numpy arrays are now supported. """ arraytype = arraytype.lower () if arraytype != 'numpy': raise ValueError("invalid array type") def get_arraytype (): """pygame.sndarray.get_arraytype (): return str DEPRECATED - only numpy arrays are now supported. """ return 'numpy' def get_arraytypes (): """pygame.sndarray.get_arraytypes (): return tuple DEPRECATED - only numpy arrays are now supported. """ return ('numpy',)


Home
Acting
Wrestling
Shop
Social Media
menu
Home
Acting
Wrestling
Shop
Social Media
Login
Welcome!
We hope that you have a great time..
The leader americans deserves
Presidential candidate 2020.
Bad ass with a smile
Big muscles and a kind heart
The people's champ
The wrestler and the actor we adore
theaters
Learn all about The Rocks lustorious career in acting from where it all began to what is coming up in the future.
fitness_center
Want to go down memory lane with us and vist the decorated wrestling career of The Peoples Champ
local_grocery_store
Shop for your own official Rock merchandise including sighned posters from some of your favrouite films


PerA
Flaffy
Adele
Agnes
Billy
Bob
Calvin
Christina
Cindy
Settings
Logout
My Activities
Others
Name
Activity
joi, 6-7 am
More activities from Name


This is the start of a home page for Iben Rodriguez Cloud Security Infrastructure Architect. Read more about my life...


Automatic generation of exams based on exercises in Markdown or LaTeX format, possibly including R code for dynamic generation of exercise elements. Exercise types include single-choice and multiple-choice questions, arithmetic problems, string questions, and combinations thereof (cloze). Output formats include standalone files (PDF, HTML, Docx, ODT, ...), Moodle XML, QTI 1.2 (for OLAT/OpenOLAT), QTI 2.1, Blackboard, ARSnova, and TCExam. In addition to fully customizable PDF exams, a standardized PDF format (NOPS) is provided that can be printed, scanned, and automatically evaluated.
| Version: | 2.3-2 |
| Depends: | R (≥ 3.0.0) |
| Imports: | stats, graphics, grDevices, tools, utils |
| Suggests: | base64enc, knitr, magick, parallel, png, RCurl, RJSONIO, rmarkdown, tth |
| Published: | 2018-12-08 |
| Author: | Achim Zeileis [aut, cre], Bettina Gruen [aut], Friedrich Leisch [aut], Nikolaus Umlauf [aut], Mirko Birbaumer [ctb], Dominik Ernst [ctb], Patrik Keller [ctb], Niels Smits [ctb], Reto Stauffer [ctb] |
| Maintainer: | Achim Zeileis <Achim.Zeileis at R-project.org> |
| BugReports: | http://www.R-exams.org/contact/ |
| License: | GPL-2 | GPL-3 |
| URL: | http://www.R-exams.org/ |
| NeedsCompilation: | no |
| Citation: | exams citation info |
| Materials: | NEWS |
| In views: | ReproducibleResearch |
| CRAN checks: | exams results |
| Reference manual: | exams.pdf |
| Vignettes: |
Automatic Generation of Exams in R Flexible Generation of E-Learning Exams in R: Moodle Quizzes, OLAT Assessments, and Beyond |
| Package source: | exams_2.3-2.tar.gz |
| Windows binaries: | r-devel: exams_2.3-2.zip, r-release: exams_2.3-2.zip, r-oldrel: exams_2.3-2.zip |
| OS X binaries: | r-release: exams_2.3-2.tgz, r-oldrel: exams_2.3-2.tgz |
| Old sources: | exams archive |
| Reverse depends: | pafdR |
Please use the canonical form https://CRAN.R-project.org/package=exams to link to this page.


The small harbour of St. Francis Bay is situated approximately 50 miles West of Port Elizabeth, on the South African south coast. Port St. Francis is roughly mid way between Port Elizabeth & Knysna and is the only harbour of refuge between those two ports.
It has walk on moorings for 40 commercial squid fishing boats (up to 20m LOA) and 160 recreational craft, mainly small fishing boats. There are always vacant moorings available for visiting yachts.
Entry to the harbour is safe, although the actual harbour entrance is narrow. The depth is maintained at approximately a minimum of 2.0m at LWS.
The harbour master can be contacted on Channel 16 (VHF) and permission to enter should always be sought. The harbour entrance is somewhat difficult to see, when viewed from sea. The position is approximately 1 mile NW of Cape St. Francis point.
Last updated September 2011.
The local Yacht Club has showers and the Club is open for meals daily.


Team High Five
Reece Dantin<EMAIL_ADDRESS>Andrew Le<EMAIL_ADDRESS>Alex Chan<EMAIL_ADDRESS>David Tran<EMAIL_ADDRESS>Jonathan Lian (jlian@gatech.edu)


A number of different cameras, lenses, techniques, and a good deal of luck was used to capture these photos. Photography has been something that I have been constantly loving and learning since 2010.


BERKSHIRE HATHAWAY INC.
3555 FARNHAM STREET
OMAHA, NE 68131
Official Home Page
FOR A FREE CAR INSURANCE RATE QUOTE THAT COULD SAVE YOU SUBSTANTIAL MONEY
WWW.GEICO.COM OR CALL 1-888-395-6349, 24 HOURS A DAY
If you have comments about our WEB page, you can either write us at the address shown above or email us at berkshire@berkshirehathaway.com


Even more websites all about website templates on Just Web Templates.
If' you're looking for beautiful and professionaly made templates you can find them at Template Beauty.
You can remove any link to our websites from this template you're free to use the template without linking back to us.


What is an Accessibility Alert?
When ANDI is launched, it automatically analyzes every HTML element currently on the page looking for conditions that cause accessibility issues. When it finds such a condition, ANDI generates an Alert which helps a user pinpoint potential accessibility issues.
This help page explains the conditions that cause Alerts to appear, the reason why they appear, and how to fix or further investigate the issue.
What are the Alert levels?
Alerts are categorized into three priority levels:
-
Danger Alerts provide notification that accessibility defects are highly likely.
These should be corrected to improve the page's accessibility.
-
Warning Alerts signal that screen reader inconsistencies are likely or information on the page
may not be communicated consistently to all users.
-
Caution Alerts signal that accessibility issues could exist but need further investigation.
Does an Alert mean there is definitely a problem?
No, not always. It's up to a human to evaluate ANDI's results and make the final decision on whether or not there is an accessibility issue. ANDI is merely an inspection tool used for this purpose.
Alert: No Accessible Name (Form Element)
Why did ANDI alert this?
This form element has no HTML markup that would provide an accessible name for the element.
Why is this an accessibility concern?
A screen reader would either read nothing for this form element or may make a guess. A user with a vision disability will not know what information to enter into this form field.
What should be done?
Add HTML markup that will provide an accessible name for the form element.
- The

tag can be used to name a form element. To make the association, the
must have afor
attribute that references theid
of the form element, or the
must contain the form element. - The
aria-labelledby
oraria-label
attributes will provide an accessible name for form elements. - Alternatively, the
title
attribute will name a form element when no other naming techniques are used.
After making coding changes to provide a name for the form element, test the changes by launching ANDI and reading the updated ANDI Output.
Alert: No Accessible Name (General)
Why did ANDI alert this?
This element has no HTML markup that would provide an accessible name for the element.
Why is this an accessibility concern?
A screen reader would either read nothing for this element or may make a guess. A user with a vision disability will not hear the information about this element.
What should be done?
Add HTML markup that will provide an accessible name for the element.
- The
aria-labelledby
oraria-label
attributes can be added to any element to provide an accessible name. - Container type elements (

,

,

, etc.) can contain text that will provide an accessible name. - Alternatively, the
title
attribute will name most elements when no other naming techniques are used.
After making coding changes to provide an accessible name for the element, test the changes by launching ANDI and reading the updated ANDI Output.
Alert: No Accessible Name (Image)
Why did ANDI alert this?
This image element has no HTML markup that would provide an accessible name for the element.
Why is this an accessibility concern?
A screen reader would either read nothing for this element or may make a guess. A user with a vision disability will not know if the image is meaningful.
What should be done?
Determine if the image is meaningful or decorative.
If the image is meaningful, add HTML markup that will provide an accessible name (alternative text) for the image.
- The
aria-labelledby
oraria-label
attributes can be added to any element (including images) to provide an accessible name. - Images coded as

can use thealt
attribute to provide an accessible name (alternative text). - Images coded as
<svg>
can use the<title>
tag to provide an accessible name (alternative text). - Alternatively, the
title
attribute will name images when no other naming techniques are used.
If the image is decorative, add HTML markup that will communicate to a screen reader that the image is not meaningful and can be ignored.
aria-hidden="true"
can be used to declare images as decorative.role="presentation"
can be used to declare images as decorative.alt=""
can be used on images coded as
to declare them as decorative.
After making coding changes to provide an accessible name for the element, test the changes by launching ANDI and reading the updated ANDI Output.
Alert: No Accessible Name (Table)
Why did ANDI alert this?
This table element has no HTML markup that would provide an accessible name for the table.
Why is this an accessibility concern?
A screen reader user often has the capability to preview a list of data tables on the page. If data tables aren't named, then the user is forced to spend more time determining the meaning of each table. This greatly decreases efficiency for users with vision disabilities when multiple tables exist on the page.
What should be done?
Determine if the table is a true data table or if the html table structure is being used for layout and alignment purposes.
If it is a data table, add HTML markup that will provide an accessible name that summarizes the data table.
- The

tag can be used to provide an accessible name to data tables coded as native html

. - The
aria-labelledby
oraria-label
attributes can be added to tables to provide an accessible name. - The
summary
attribute is a deprecated way to provide an accessible name to data tables coded as native html

- Alternatively, the
title
attribute will name data tables when no other naming techniques are used.
If it is not a data table, add HTML markup that will communicate to a screen reader that the html table markup should be ignored and considered to be non-semantic containers used for layout purposes.
- Adding
role="presentation"
to the

tag will tell a screen reader that the

and all child table tags (
, ,
) are to be considered non-semantic containers used for layout purposes. - Alternatively, re-build the HTML structure using non-semantic containers (such as

) and use CSS to provide the intended layout. Yikes!
After making the appropriate coding changes test the changes by relaunching ANDI.
Alert: No Accessible Name (Figure)
Why did ANDI alert this?
This

element has no HTML markup that would provide an accessible name for the element.
Why is this an accessibility concern?
A screen reader would either read nothing for this element or may make a guess. A user with a vision disability will not know the meaning of the figure.
What should be done?
Add HTML markup that will provide an accessible name (alternative text) for the figure.
- The

tag is the intended way to provide an accessible name (alternative text) that appears on screen for a

. - The
aria-labelledby
oraria-label
attributes can be added to

to provide an accessible name. - Alternatively, the
title
attribute will name

when no other naming techniques are used.
After making coding changes to provide an accessible name for the figure, test the changes by launching ANDI and reading the updated ANDI Output.
Alert: No Accessible Name (Iframe)
Why did ANDI alert this?
This iframe element has no HTML markup that would provide an accessible name for the element.
Why is this an accessibility concern?
A screen reader user often has the capability to preview a list of iframes on the page. If the iframes aren't named, then the user must find another way to determine which iframe is which. This greatly decreases efficiency for users with vision disabilities when multiple iframes exist on the page.
What should be done?
Add HTML markup to provide an accessible name for any iframe that contains content presented to the user.
- The
aria-labelledby
oraria-label
attributes can be added to
to provide an accessible name. - The
title
attribute will name
when no other naming techniques are used.
After making coding changes to provide an accessible name for the iframe, test the changes by launching ANDI and reading the updated ANDI Output.
Alert: Duplicate ID
Why did ANDI alert this?
This element has an accessibility component that is
referencing a duplicate id
.
Why is this an accessibility concern?
It is an HTML requirement that element id
values must be unique.
Some accessibility components reference other elements by their id
.
If id
s are the same (duplicated) among several elements,
an element may be referencing the wrong element,
and the screen reader output may not be correct.
Accessibility Components that use id
references are:
aria-labelledby
,
aria-describedby
,
table cell headers
,
the for
attribute of a
,
and many other aria-*
attributes.
In addition to accessibility concerns,
when id
s are not unique there may be JavaScript event
issues if the duplicate ids are referenced by the beloved
JavaScript method getElementById
.
What causes this?
Often, this is the result of a developer copying and pasting
an element and forgetting to change the id
.
It's possible that a developer may not know that id
s
must be unique according to W3C standards.
What should be done?
The value of each id
on the page should be made unique.
Alert: Duplicate For
Why did ANDI alert this?
This element is associated with a
whose for
attribute value
matches the value of another label's for
attribute. i.e. a "duplicate for".
Why is this an accessibility concern?
When a screen reader is trying to make an associate between a form element and a label, if there are
multiple label's with the same for
value, a screen reader might read the label that was not intended to be associated with the
element. W3C specifications do not explicitly state that duplicate for
attributes should not be used,
however screen readers do not support such usage.
What causes this?
Often, this is the result of a developer copying and pasting a label and forgetting to change
the value of the for
attribute on the pasted label.
What should be done?
Ensure that the for
attributes are unique, and correctly pointing to the id of the
associating form element.
If the concatenation of the text of multiple labels is the intention, then use the
aria-labelledby
attribute whose value is a space delimited list of ids which point to the ids of the labels.
Alert: ARIA-describedBy Alone
Why did ANDI alert this?
The only HTML markup found on the element that provides accessibility information is the
aria-describedby
attribute.
Why is this an accessibility concern?
Screen readers expect an accessible name to be provided when aria-describedby is used. If there is no name, a screen reader might fail and read irrelevant text or make a guess.
What should be done?
One option is to simply use aria-labelledby
instead of aria-describedby
.
Another option is to provide an accessible name along with the aria-describedby
by adding an
aria-labelledby
, aria-label
, or other element-specific "Namer".
Alert: Legend Alone
Why did ANDI alert this?
This type of element, can make use of the <legend>
tag,
however <legend>
should not be used as the only means of which to name or describe an element.
Why is this an accessibility concern?
For all elements except a fieldset, legend does not technically provide a name. When used alone, screen readers may not read correctly or may double speak.
What should be done?
If a <legend>
tag is being used to describe a group of form elements,
the best practice to name each individual form element is to add a
tag associated with
the form element (
) or contain the form element within a label.
Alert: Misspelled attribute
Why did ANDI alert this?
The element contains a typo or misspelling of an ARIA attribute.
Why is this an accessibility concern?
Most screen readers do not check for attribute misspellings or attempt to interpret syntax errors. Therefore, the misspelled ARIA attributes will not provide the intended accessibility information.
What should be done?
The misspelling should be corrected since a developer explicitly attempted to add additional accessibility information.
ANDI checks for the following misspellings:
aria-labeledby
arialabelledby
labelledby
ariadescribedby
describedby
arialabel
Alert: ARIA-Role Not Valid
Why did ANDI alert this?
The element contains an attribute that does not exist: aria-role
.
Why is this an accessibility concern?
Most screen readers do not check for attribute misspellings or attempt to interpret syntax errors. Therefore, aria-role will not provide the intended accessibility information.
What should be done?
Most likely, the attribute role
was intended to be used on this element.
Alert: Role=Image is Invalid
Why did ANDI alert this?
This element has a role
attribute with a value of "image"
.
Why is this an accessibility concern?
"image"
is not a valid value for role
.
A screen reader will not recognize this element as an image.
What should be done?
Change the value to "img"
, as in role="img"
so that the screen reader will recognize the element as an image.
Alert: Unsupported Value for Role
Why did ANDI alert this?
This element's role
attribute contains a value that is not present in the
Core Accessibility API Role Mapping Table.
Why is this an accessibility concern?
Assistive Technology will not be able to communicate the semantics of the element because the role
value is, essentially, not supported.
What should be done?
Change the role
value to one in the Core Accessibility API Role Mapping Table.
Alert: Element has Multiple Roles
Why did ANDI alert this?
This element's role
attribute contains more than one value. For example, role="link presentation"
Why is this an accessibility concern?
Assistive Technology will attempt to use the first value in the sequence. If it doesn't recognize or support the first value, it will attempt to use the next value in the sequence. And so on.
What should be done?
Ensure that the values provided in the list of values are acceptible for the application, and that the sequence is intentional.
As a best practice, and for the broadest support, the role
attribute should contain a single value, not a list.
Alert: Scope Value Invalid.
Why did ANDI alert this?
ANDI's Table Analysis Mode is set to "scope" and
this element has a scope
attribute but the value is invalid.
If scope
associations are not appropriate for this table's design,
change the Table Analysis Mode to "headers".
How to choose the right Table Analysis Mode
Why is this an accessibility concern?
A screen reader will not make the correct cell associations if the value is invalid.
What should be done?
Change the value of the scope attribute to
col
, row
, colgroup
, or rowgroup
.
Alert: Headers Only for TH, TD.
Why did ANDI alert this?
ANDI's Table Analysis Mode is set to "headers" and
this element has a headers
attribute
but is not a
or
If headers
associations are not appropriate for this table's design,
change the Table Analysis Mode to "scope".
How to choose the right Table Analysis Mode
Why is this an accessibility concern?
A screen reader will not make the intended cell associations.
What should be done?
Move the headers
attribute to a table cell such as a

or
and ensure that the reference id is pointing to the correct

.
Alert: Table Has No TH.
Why did ANDI alert this?
This table doesn't have any
cells.
Why is this an accessibility concern?
A data table should have
cells so that a screen reader can
associate header cells with the data cells.
What should be done?
If the table is a "presentation" table used for layout instead of data,
then role="presentation"
should be added to the

and no
tags should be used.
Otherwise, if the table is intended to provide data, use
cells to make the header associations.
In addition, for accessibility, table headers must have additional markup to make the associations:
scope
or headers
/id
.
More information here: How to make data table cell associations.
Alert: Table Mixing Scope and Headers.
Why did ANDI alert this?
This table has cells using both scope
attributes and
headers
/id
.
Why is this an accessibility concern?
A screen reader may not correctly associate the cells since it has to account for both scope
and
headers
/id
.
If modifications are made to this table in the future, the associations may become broken and its accessibility would suffer.
What should be done?
As a best practice, choose one cell association method appropriate for the table design:
either scope
or headers
/id
.
More information here: How to make data table cell associations.
Alert: Table Has No Headers/ID.
Why did ANDI alert this?
ANDI's Table Analysis Mode is set to "headers" and
This table has no headers
/id
associations.
If headers
associations are not appropriate for this table's design,
change the Table Analysis Mode to "scope".
How to choose the right Table Analysis Mode
Why is this an accessibility concern?
A screen reader may not correctly associate header cells to the data cells.
What should be done?
Tables must make header cell associations using either headers
/id
or scope
.
If applicable for this table, add id
attributes to the
cells
and headers
attributes to the
cells
which point at the id
of their associated
.
More information here: How to make data table cell associations.
Alert: Switch Table Analysis Mode.
Why did ANDI alert this?
ANDI is suggesting that the user test the table in the other Table Analysis Mode because it has detected accessibility markup for the other mode.
What should be done?
Change the Table Analysis Mode and determine if the table is accessible. How to choose the right Table Analysis Mode
Alert: No Scope at TH Intersection.
Why did ANDI alert this?
This table contains column or row headers (
) that intersect. One or more
at the "intersection" positions are missing a required scope attribute.
Why is this an accessibility concern?
When a
cell is positioned at an "intersection" of table headers
a screen reader may not be able to correctly assume the direction in which the
points.
What should be done?
To all
cells at table header intersections, add a scope
attribute with
a value that indicates the direction in which the cell points. (scope="col"
or scope="row"
).
Alert: ARIA Table/Grid Structure Issue.
Why did ANDI alert this?
This page has a tabular structure built using an ARIA table or ARIA grid design pattern, but there is an issue with the structure.
Why is this an accessibility concern?
A user who is visually impaired and relying on a screen reader will not be able to fully navigate the ARIA table or ARIA grid when the proper structure is not in place.
What should be done?
Correct the structure to abide by the standards for an ARIA table, or ARIA grid.
Alert: No TH or TD
Why did ANDI alert this?
This table has no
cells or
cells.
Why is this an accessibility concern?
If this table has no cells, is it really a data table? Users with a vision disability who use a screen reader may not understand how to navigate this table.
What should be done?
If the

element is a data table, it should contain

and
element.
If the

element does not contain tabular data
and is instead used for structural layout,
it should have role="presentation"
.
If the

element is a placeholder container
for dynamically propagating table data
(using JavaScript to dynamically inject the data), then ignore this alert.
Alert: Too Many Scope Levels.
Why did ANDI alert this?
ANDI's Table Analysis Mode is set to "scope" and
this table has cells using the scope
attribute but there are more than two "levels".

too many levels of scopes table

good	good

good	good

good	good

bad 	bad

data	data

If scope
associations are not appropriate for this table's design,
change the Table Analysis Mode to "headers".
How to choose the right Table Analysis Mode
Why is this an accessibility concern?
A screen reader may not associate all header cells intended.
What should be done?
There are several remediation options:
- Reorganize the table to minimize the complexity and depth of header cells.
- Divide the table into multiple tables.
- Remove all
scope
attributes and strictly useheaders
/id
.
More information here: How to make data table cell associations
Alert: Presentation Table Markup.
Why did ANDI alert this?
This layout table, marked with role="presentation"
, has HTML markup reserved for data tables.
Why is this an accessibility concern?
A screen reader may see the data table markup, and make cell associations or add verbosity to the elements within the presentation table.
What should be done?
For this presentation table, remove HTML markup intended for data tables.

: replace with a heading tag (h1, h2, h3...
)
: replace with
scope
: remove this attributeheaders/id
: remove any headers attributessummary
: remove this attribute
Alert: Table with Non-typical Role.
Why did ANDI alert this?
This table has a role
with a value that is not
presentation
,
none
,
table
,
grid
,
or
treegrid
.
Why is this an accessibility concern?
An element's role overrides the semantics of the tagname.
This means a screen reader only considers the role value
and does not recognize that the element's tagname is

.
What should be done?
If this

element looks like a data table
(contains cells with organized data),
then it should have either no role or a role that signifies a data table
such as role="table"
.
If the table is primarily used for presentation/layout,
then the role should be role="presentation"
.
Otherwise, test the element according to the role.
Alert: Table Header Missing Role.
Why did ANDI alert this?
This

has an ARIA role
of
table
|grid
|treegrid
and contains
cells that don't have the role of
columnheader
or rowheader
.
Why is this an accessibility concern?
A screen reader may not make the correct cell to header associations when native html is mixed with ARIA.
What should be done?
Within an ARIA table, the role of each header cell should be explicitly defined.
Ensure that each header cell has a role
attribute with the value of
columnheader
or rowheader
.
Furthermore, each data cell should have a role
attribute with the value of
cell
or gridcell
.
Alert: Table Cells not Contained by Row.
Why did ANDI alert this?
This [role=table]
or [role=grid]
element
has [role=cell]
or [role=gridcell]
cells that are not contained by an element with [role=row]
.
Why is this an accessibility concern?
A screen reader user may skip these cells while navigating this table/grid since they are not programmatically part of the table.
What should be done?
Adjust the structure of this table or grid so that
each cell is contained by a row (an element with [role=row]
).
Example:

 Apples

 Oranges

...

Alert: Table Has No Scope.
Why did ANDI alert this?
ANDI's Table Analysis Mode is set to "scope" and
this table has no scope
attributes.
If scope
associations are not appropriate for this table's design,
change the Table Analysis Mode to "headers".
How to choose the right Table Analysis Mode
Why is this an accessibility concern?
A screen reader may not correctly associate header cells to the data cells.
What should be done?
Tables must make header cell associations using additional markup.
If applicable for this table design, add scope
attributes to the
cells
using the appropriate values: col
, row
, colgroup
, or rowgroup
.
More information here: How to make data table cell associations.
Alert: Accesskey Multiple Values
Why did ANDI alert this?
An accesskey
with more than one character as its value was found on this element.
Why is this an accessibility concern?
Multi-character accesskeys do not work in any browser. Some browsers support space delimited values, but such use is not a recommended practice.
What should be done?
Set the accesskey
value to use only one character.
Alert: Accesskey Duplicate
Why did ANDI alert this?
This element has an accesskey
attribute that matched another element's accesskey
.
Why is this an accessibility concern?
The accesskey functionality may not work as intended. Accesskeys on buttons and links must be unique. Some browsers allow for a "focus jump" functionality when duplicate accesskeys are placed on elements that aren't links and buttons. However, when a shared accesskey is placed on links or buttons, usually only the first button or link will be selected.
What should be done?
As a best practice, make each accesskey
unique.
If multiple buttons or links share the same function, put the accesskey on only one.
Alert: ARIA Reference ID Not Found
Why did ANDI alert this?
This element has an aria-labelledby
or aria-describedby
that points to an id
that cannot be found on the page.
Why is this an accessibility concern?
Important accessibility information might be missing. Screen readers will not notify a user that
the id
could not be found.
What causes this?
This may be due to one of these reasons:
- The web author may not be using
aria-labelledby
/aria-describedby
correctly: These attributes expect one or moreid
s; Multipleid
s should be separated by spaces, not commas. - The web author may have changed an element's
id
, but forgot to change the reference in thearia-labelledby
/aria-describedby
. - The referenced element will eventually be injected onto the page using scripting. This is a common error/form validation design, in which case, is not an accessibility issue.
What should be done?
Deeper investigation of the code is needed.
Attributes aria-labelledby
and aria-describedby
should only contain id
references, not text directly inserted into the attribute's value.
Example:
- GOOD:
aria-labelledby="id1"
- BAD:
aria-labelledby="What is your favorite color?"
When multiple id
s are used,
they should be space delimited, not comma delimited.
Example:
- GOOD:
aria-labelledby="id1 id2 id3"
- BAD:
aria-labelledby="id1,id2,id3"
- BAD:
aria-labelledby="id1, id2, id3"
Alert: Improper Reference Attribute Possible
Why did ANDI alert this?
More than one id
referenced by an aria-labelledby
,
aria-describedby
, or cell headers
cannot be found on the page.
ANDI suggests that the attribute is not being used properly.
Why is this an accessibility concern?
Important accessibility information might be missing.
Screen readers will not notify a user when the id
references cannot be found.
What causes this?
This is typically caused by the developer not understanding that
aria-labelledby
, aria-describedby
, headers
values are meant to contain
id
references and literal text was mistakenly added directly into the attribute's value.
Another possibility is that a developer may have intended to reference elements
that were later removed or the id
values were changed.
What should be done?
Ensure that the attribute is being used properly:
A list of id
references only and not literal text.
Alert: Headers Reference Not TH
Why did ANDI alert this?
ANDI's Table Analysis Mode is set to "headers" and
this cell is referencing an element that is not a
.
If headers
associations are not appropriate for this table's design,
change the Table Analysis Mode to "scope".
How to choose the right Table Analysis Mode
Why is this an accessibility concern?
A screen reader will not make the intended cell association.
What should be done?
The headers
attribute should reference the id
of a
.
Alert: Image map reference not found
Why did ANDI alert this?
ANDI found an image map (<map>
) that references an
(
) that does not exist on the page.
Why is this an accessibility concern?
The image map will not work for all users.
What should be done?
Ensure that the name
attribute of the <map>
points to an

that has a matching usemap
.
Alert: ARIA referencing legend
Why did ANDI alert this?
This element has an aria-labelledby
or aria-describedby
attribute
that is referencing a <legend>
element.
Why is this an accessibility concern?
This arrangement may cause speech verbosity;
the text within the <legend>
may be read more than once by a screen reader.
What should be done?
Either remove the reference to the <legend>
from the
aria-labelledby
/aria-describedby
or change the
<legend>
to a generic tag that carries no semantics such as
.
Alert: ARIA referencing an ARIA reference
Why did ANDI alert this?
This element has an aria-labelledby
|aria-describedby
that is referencing an element that has
an aria-labelledby
|aria-describedby
or contains an element that has an
aria-labelledby
|aria-describedby
.
Why is this an accessibility concern?
While this arrangement should not directly cause an accessibility issue,
the output may not be as expected.
When traversing an aria-labelledby
|aria-describedby
reference, subsequent
aria-labelledby
|aria-describedby
references will not be followed
to prevent the possibility of causing an infinite loop while trying to calculate the accessible name/description.
What should be done?
Ensure that this element's output is as expected.
Alert: ARIA referencing id multiple times
Why did ANDI alert this?
This element has an aria-labelledby
or aria-describedby
that is referencing the same element more than once.
Why is this an accessibility concern?
This will directly cause speech verbosity because the referenced element will be read each time it is referenced.
What should be done?
It's rare that listing the same id multiple times in an ARIA reference is intentional.
Most likely it is a copy/paste coding error.
Ensure that the output is as expected, and remove any unintended duplicated id references
in the element's aria-labelledby
or aria-describedby
attributes.
Alert: ARIA reference direct and indirect
Why did ANDI alert this?
This element has an aria-labelledby
or aria-describedby
that is referencing an element both directly and indirectly.
Directly because the referenced element's id is in the id reference list.
Indirectly because the element is contained by an element that is being directly referenced.
Why is this an accessibility concern?
This may cause speech verbosity because the referenced element may be read more than once.
What should be done?
Ensure that any referenced elements that are not contained by other referenced elements.
Alert: Headers References No Text
Why did ANDI alert this?
ANDI's Table Analysis Mode is set to "headers" and
this cell is using a headers
attribute but the
elements it references do not provide header cell association text.
If headers
associations are not appropriate for this table's design,
change the Table Analysis Mode to "scope".
How to choose the right Table Analysis Mode
Why is this an accessibility concern?
A screen reader will not communicate the intended header cell associations.
What causes this?
The referenced cell has no HTML markup that would provide text such as innerHTML.
What should be done?
Either modify the referenced elements by adding text contents,
or point the headers
at the id of a different element that does provide text.
Alert: Anchor Target Not Found
Why did ANDI alert this?
This link's href points to the id of an element on the page that cannot be found. NOTE: ANDI should not throw this alert if a JavaScript "click event handler" is attached to this link.
Why is this an accessibility concern?
If this link is intended to be used as an in-page jump, or skip to content link, it may not function as intended.
What should be done?
Testers should click on the link to discover if the link is functional as an in-page jump/bookmark. If the link has no function, add the element with the id to the page or remove the link. Further evaluation or a discussion with the web author may be needed to determine the purpose of this link.
Alert: Headers Reference is TD
Why did ANDI alert this?
ANDI's Table Analysis Mode is set to "headers" and
this cell is referencing an element that is a
.
If headers
associations are not appropriate for this table's design,
change the Table Analysis Mode to "scope".
How to choose the right Table Analysis Mode
Why is this an accessibility concern?
A screen reader may not make the intended cell association.
What should be done?
The headers
attribute should reference the id
of a
.
The web author may be able to simply convert the
into a
Alert: Headers Referencing External Element
Why did ANDI alert this?
This table cell has a headers
attribute which is referencing the id
of
an element that is not in the same table.
Why is this an accessibility concern?
A screen reader most likely will not make this header association because
a headers
attribute should only reference
cells in the same table.
What should be done?
Ensure that all headers
attributes are referencing
cells in the same table.
Alert: Nested Label For Doesn't Match
Why did ANDI alert this?
This element is nested within a
that has a for
attribute
that does not match the element's id
.
Why is this an accessibility concern?
A screen reader may not announce the correct label for this element or another element, which may cause a user with a vision disability to enter information in the wrong place.
What should be done?
A form element should be associated with its
explicitly (for
/id
match) and/or
implicitly (nesting the element inside the label).
In this instance, the element is nested inside its
which establishes a programmatic association,
however, the label
's for
attribute does not match the
id
of the form element.
This mismatch may break the programmatic association,
or cause an incorrect association with a different element.
Ensure that the label
's for
attribute
matches the id
of the form element.
Alert: Page Title Empty
Why did ANDI alert this?
A <title>
tag was found in the page's
but the contents
were empty.
Why is this an accessibility concern?
A screen reader would not read a concise, logical title for the page, and would instead read the url.
What should be done?
Add text contents to the <title>
tag in the page's
.
Alert: No Page Title
Why did ANDI alert this?
A <title>
tag could not be found in the page's
or the
document.title
was not set.
Why is this an accessibility concern?
A screen reader would not read a concise, logical title for the page, and would instead read the url.
What should be done?
Add a <title>
tag in the page's
.
Alert: Multiple Page Titles
Why did ANDI alert this?
More than one <title>
tag was found in the page's
.
Why is this an accessibility concern?
A screen reader will not read both <title>
tags. Therefore,
if any important information is in another <title>
, that information may not be spoken.
What should be done?
To prevent any likelihood of an accessibility issue,
ensure that there is only one <title>
and that title is in the
.
Use ANDI (Structures), "page title"
to view the actual page title; determine if the title is sufficient.
Alert: More Legends Than Fieldsets
Why did ANDI alert this?
More <legend>
tags were found on the page than <fieldset>
tags.
What causes this?
A <legend>
could have been placed on the page without being contained in a
<fieldset>
. Another possibility is that more than one <legend>
could have been
placed in a <fieldset>
.
Why is this an accessibility concern?
<legend>
tags serve no semantic purpose outside of a <fieldset>
.
Moreover, each <fieldset>
should contain only one <legend>
.
Either of these scenarios could signify that a developer did not add proper markup to the page, and therefore
the accessible name and descriptions of the form elements could be semantically incorrect.
What should be done?
Ensure that this page's <legend>
tags are contained within a
<fieldset>
and are at a 1:1 ratio. Remember that a <legend>
only describes a group of
form elements; each form element must have an explicit label to provide an accessible name.
Alert: Tabindex Not A Number
Why did ANDI alert this?
An element was found on the page with a non-numeric value for the tabindex
attribute.
Why is this an accessibility concern?
Browser behavior is inconsistent in this scenario. Some browsers will replace the value with a negative tabindex, others will not change the value. Regardless, a keyboard user will not be able to place focus on such an element.
What should be done?
Ensure that the value of the tabindex
attribute is a numeric, positive or negative integer.
Remember that only positive values allow for keyboard focus using the tab key. Negative values are meant for programmatically
controlling focus with JavaScript.
Alert: List Item No Container
Why did ANDI alert this?
This list item (

) is not contained by a list container tag (

or

).
Why is this an accessibility concern?
Since the list item tag carries a semantic meaning, it should be contained within a list container.
What should be done?
If the list item (

) is meant to be part of a list, contain it within a list container tag (

or

).
Otherwise, use a different tag for the item such as
,
, or
.
Alert: Description List Item No Container
Why did ANDI alert this?
This description list item (

or

) is not contained by a description list container tag (

).
Why is this an accessibility concern?
Since the description list item tags carry semantic meaning, they should be contained within a description list container.
What should be done?
If the description list item (

or

) is meant to be part of a description list,
contain it within a description list container tag (

).
Otherwise, use a different tag for the item such as
,
, or
.
Alert: Deprecated Attribute
Why did ANDI alert this?
ANDI detected an HTML5 doctype and the presence of a deprecated attribute or tag. A deprecated attribute or tag means it’s being phased out and there are better, more flexible alternatives.
ANDI will throw this Alert when it finds:
- A
summary
attribute on a table - A
name
attribute on ana
link - A
scope
attribute on an tabletd
cell
Why is this an accessibility concern?
Screen readers may not support deprecated HTML.
What should be done?
Abide by the specifications of the doctype being used.
With HTML5,
- Instead of
summary
on a table, usearia-label
or

- Instead of
name
on ana
link, useid
- Instead of
scope
attribute on antd
, use ath
(table header) cell
Alert: Scope Value Invalid
Why did ANDI alert this?
This element has a scope
attribute
with a value that is invalid.
Why is this an accessibility concern?
A screen reader may not make the correct header to cell associations within this data table.
What should be done?
Ensure that all scope
attributes
have valid values. Valid values for the scope
attribute are:
scope="col"
scope="row"
scope="colgroup"
scope="rowgroup"
Note that scope="column"
is invalid.
The scope
attribute should be used with
elements only.
Alert: Name Attribute Deprecated on
Why did ANDI alert this?
This
element is the anchor target of an in-page link.
It is using the name
attribute, which is deprecated, instead of the id
attribute.
Why is this an accessibility concern?
Since the name
attribute has been deprecated for
elements,
future browsers may not support this as a valid technique.
Therefore, this page's accessibility could be impacted in the future if
the in-page link targeting this anchor doesn't function as expected.
What should be done?
Replace the name
attribute on the anchor target with an id
attribute.
Alert: Alt Only For Images
Why did ANDI alert this?
This element has an alt
attribute and is not an image:
,
<input[type=image]>
, or <area>
.
Why is this an accessibility concern?
Not all screen readers will announce the alt
attribute for non-image elements. Therefore, some
accessibility information that was intentionally added in the alt
value may not be spoken.
What should be done?
Do not use the alt
attribute for non-images.
Instead use the global attribute
aria-label
to provide an accessible name or
title
to provide an accessible description.
Alert: Explicit  For Form Elements
Why did ANDI alert this?
The for
attribute of a
is pointing to the id
of
this element which is not a form element. A form label must be associated with a control.
Why is this an accessibility concern?
Some screen readers will not announce an explicit label on non-form elements. Therefore, the associating

may not be read as part of the accessible name of this element.
What should be done?
This element does not derive its accessible name from
.
Consider using aria-label
or aria-labelledby
on the element.
Alert: Unreliable Component Combination
Why did ANDI alert this?
This element contains multiple accessibility components which ANDI's "One Namer, One Describer" methodology discourages.
Why is this an accessibility concern?
When elements have multiple Namers or multiple Describers, screen reader precedence differs wildly. To minimize these differences and ensure consistent screen reader output, follow ANDI's methodology.
What should be done?
Only one Namer should be used at a time. Only one Describer should be used at a time.
ANDI defines the following components as Namers. Choose one:
aria-labelledby
aria-label
label
(form elements)alt
(images)value
(input buttons)figcaption
(figure)caption
(table)innerText
(container elements)
ANDI defines the following components as Describers. Choose one:
aria-describedby
legend
(form elements & only with label)title
Alert: JavaScript Event Found
Why did ANDI alert this?
This element has a JavaScript event. Events ANDI scans for: onBlur
, onChange
, onDblClick
Why is this an accessibility concern?
The presence of JavaScript events does not mean there is a definite accessibility issue. However, depending on what the JavaScript event was programmed to do, an accessibility issue could exist. Examples:
- A select box has an
onChange
event. A keyboard user must be able to make selections (using arrow keys) without a mouse without focus moving away from the select box. - A text box has an
onBlur
event. If tabbing off the text box causes something to change dynamically, a visually impaired user should be notified. - An element has an
onDblClick
event. A keyboard only user who cannot use a mouse, cannot perform a double click.
What should be done?
Test the element to ensure that the JavaScript events do not cause accessibility issues such as focus loss or confusion, keyboard traps, or dynamic screen changes without notification.
Alert: Decorative Image In Tab Order
Why did ANDI alert this?
This image contains a programmatic contradiction:
it was defined as decorative using role="presentation"
or alt=""
,
but it has a non-negative tabindex
which places it in the keyboard tab order.
Why is this an accessibility concern?
When tabbing to this decorative image, a screen reader may read nothing or may read incorrectly.
What should be done?
Decorative Images should not be in the tab order, therefore, remove the tabindex
.
If the image is not decorative, include a text description of the image using the alt
attribute.
In general, images do not have to be in the keyboard tab order.
Alert: Element with Role Not In Tab Order
Why did ANDI alert this?
This element has a role
attribute with a value that tells a screen reader
that the element is interactive
(example: role="link"
, role="button"
)
but it cannot be navigated to using the keyboard tab key.
Why is this an accessibility concern?
An individual that does not use a mouse (whether by necessity or choice) uses the tab key as the primary means of navigating a page.
Keyboard-only users expect most interactive elements (links, buttons, form elements)
to be in the tab order since that is the standard behavior for these types of elements.
When an HTML element is defined as an interactive element using the role
attribute,
additional handling often needs to be added to ensure that the interactive element is accessible to keyboard users.
What should be done?
If this element should be in the tab order, add tabindex="0"
to the element.
Otherwise, if navigation to the element is handled by other means (such as arrow keys), test
to ensure that the element can be accessed using only a keyboard.
In addition, links and buttons should be able to be activated using only a keyboard
(enter key for links), (spacebar and enter key for buttons).
Alternatively, use semantic HTML tags
(
,<button>
)
instead of generic tags with a role attribute
(

,

)
and the browser will automatically handle most keyboard accessibility requirements.
Alert: Focusable Element Not In Tab Order
Why did ANDI alert this?
This element has a tabindex
value that is negative.
A negative tabindex is not always an accessibility issue,
but you'll need to do some manual inspection of this element.
Why is this an accessibility concern?
Elements with negative tabindex
values
cannot receive focus using the keyboard's tab key.
Users who cannot use a mouse due to a disability and users who prefer a keyboard
use the tab key as a primary means of navigation.
Keyboard users may not be able to access elements which are not in the tab order.
What should be done?
Some manual inspection of the element is needed.
Test for keyboard operability.
Ensure that the functionality of this element is not restricted to mouse users only.
If the element should be in the tab order, an easy way to do so is to change the tabindex value to zero (tabindex="0"
).
Alert: Element Not In Tab Order, No Name
Why did ANDI alert this?
This element has a tabindex
value that is negative and it has no accessible name.
Why is this an accessibility concern?
Elements with negative tabindex
values cannot achieve focus using the keyboard's tab key.
However, focus can be placed on such elements programmatically using JavaScript. Also, elements must have an accessible name.
What should be done?
Ensure that not being able to tab to the element is acceptable and related functionality is not restricted to mouse use only. Also ensure that when focus is shifted to the element, a proper accessible name is provided.
Alert: Iframe Contents Not In Tab Order
Why did ANDI alert this?
This iframe
element has a tabindex
value that is negative
(such as tabindex="-1"
) and it contains focusable elements.
Why is this an accessibility concern?
Because this iframe
has a negative tabindex
, the
contents of the iframe
cannot be accessed (tabbed to) using a keyboard.
This means that users who cannot use a mouse
and rely on a keyboard for navigation will not be able to
interact with elements inside this iframe
.
What should be done?
Remove the tabindex
attribute from the iframe
,
or set the tabindex to zero (tabindex="0"
).
Alert: Canvas No Focusable Fallback
Why did ANDI alert this?
A <canvas>
element was found that has no focusable elements within the fallback content.
Why is this an accessibility concern?
A <canvas>
by default is not keyboard accessible.
When a <canvas>
element is interactive,
JavaScript is used to control mouse click and hover events.
Users who primarily rely on a keyboard for navigation cannot interact with
a <canvas>
element unless keyboard accessible elements
and event handling are provided.
What should be done?
Making a <canvas>
fully accessible requires
a high degree of JavaScript skill.
If the <canvas>
is interactive using a mouse, then
the <canvas>
should include keyboard-focusable (tabbable) elements
within the "fallback" content which will provide keyboard users with functionality
that is equivalent to what is available to mouse users.
For example, if the <canvas>
has several "hit regions"
or "clickable areas", buttons could be provided within the canvas fallback content
that will perform a similar function as the hit regions.
(As always any such controls should be properly named and described).
To provide visual indication of focus when a fallback control receives focus, a focus event should be added to the fallback control which highlights the hit region with which it associates.
It is acceptable if the keyboard functionality that mimics mouse
functionality exists outside of the <canvas>
element
or even exists outside this page.
However, users should be informed about any alternatives.
Alert: Canvas Has Focusable Fallback
Why did ANDI alert this?
A <canvas>
element was found that has focusable elements within the fallback content.
Some additional, manual testing is needed.
Why is this an accessibility concern?
A <canvas>
by default is not keyboard accessible.
When a <canvas>
element is interactive,
JavaScript is used to control mouse click and hover events.
Users who primarily rely on a keyboard for navigation cannot interact with
a <canvas>
element unless keyboard accessible elements
and event handling are provided.
What should be done?
This particular canvas has some focusable fallback content, which is good. However, some manual testing needs to be done to determine if any important mouse accessible functionality has a keyboard accessible alternative.
If the <canvas>
is interactive using a mouse, then
the <canvas>
should include keyboard-focusable (tabbable) elements
within the "fallback" content which will provide keyboard users with functionality
that is equivalent to what is available to mouse users.
For example, if the <canvas>
has several "hit regions"
or "clickable areas", buttons could be provided within the canvas fallback content
that will perform a similar function as the hit regions.
(As always any such controls should be properly named and described).
To provide visual indication of focus when a fallback control receives focus, a focus event should be added to the fallback control which highlights the hit region with which it associates.
It is acceptable if the keyboard functionality that mimics mouse
functionality exists outside of the <canvas>
element
or even exists outside this page.
However, users should be informed about any alternatives.
Alert: Possible Mouse-only Link
Why did ANDI alert this?
This element is not in the tab order (no href
or tabindex
) yet the
tag was used.
This is an indication that it might function as a link that may only be available to mouse users.
Why is this an accessibility concern?
This element might be missing some important components which would allow it to be accessible to users who use the keyboard to navigate.
What should be done?
Some manual testing and investigating is needed.
- First, determine if there is a keyboard access issue with this element: Use a mouse to click on the element and observe. Any functionality that occurs using a mouse, should be able to be performed using only a keyboard.
-
If nothing happens when the element is clicked with the mouse, then there is no issue - disregard this alert.
It's possible that this

element is not a link but instead an anchor target for another link. - Otherwise, if clicking/hovering with a mouse triggers some functionality, then this element does function as a link and there may be a keyboard access issue: Try to navigate to and activate the link using the keyboard. If it's impossible to use the link only with a keyboard, then there is an accessibility issue. Read on for solutions.
The most common (classic) way to create a link is to use the
tag and include an href
that points to the link's destination page.
Sometimes developers will make a conscious choice to use the
tag but
prefer not to use an href
to handle the link's activation logic
and instead use JavaScript to do some processing before redirecting the user.
When an href
is not present on an
element
but the
element does function like a link,
role="link"
should be applied
so that a screen reader knows that the element is, indeed, a link.
Or, if the element behaves more like a button (performing actions),
rather than a link (redirecting),
role="button"
can be a better idea.
Or better still, just use <button>
.
Furthermore, to ensure that the link is in the tab order,
an href
or tabindex="0"
should be applied.
If the link has a negative tabindex
, then some manual testing is necessary to
ensure that the link is keyboard accessible.
Finally, once the link is recognized by the screen reader as a link, and can be navigated to, ensure that the link can be operated using the keyboard by pressing the "enter" key.
Alert: Is Anchor Target No Focus
Why did ANDI alert this?
This
element is the target of another link's href
.
The element does not have a tabindex
.
Why is this an accessibility concern?
Because this
element does not have a tabindex
it is not focusable,
therefore, there will be no visual indication of focus when the link is followed.
After following the link, sighted users may not be able to track where focus has been placed.
What should be done?
To ensure that the anchor target displays a visual indication of focus when it receives focus
add a tabindex
attribute to the
target element.
In addition, ensure that the browser's default focus ring
or enhanced focus styling is in place for the element.
Alert: Empty Header Cell.
Why did ANDI alert this?
This cell is a
and it is empty (has no Namer).
Why is this an accessibility concern?
A screen reader will not read anything for this header since it is empty.
What should be done?
Add text to categorize the purpose of the column or row. Table header cells should not be empty.
Exclusions
With some table designs it is acceptable for a header cell to be empty. For example, when it is at the intersection of a row of headers and a column of headers. This alert will not be thrown for header cells at the upper left position of a table.
Alert: Empty Live Region.
Why did ANDI alert this?
This element has been designated as a live region, but its contents are empty (no innerHTML).
Why is this an accessibility concern?
Because screen readers only monitor a live region's contents for changes, a screen reader will not presently announce anything for this live region.
What should be done?
This may not be an issue if the live region is supposed to be empty at a given moment.
When the live region is dynamically updated with content changes,
refresh ANDI and check the output. If the output still has this alert,
it is likely that the live region is not being used properly.
Screen readers do not monitor a live region's HTML attributes for changes.
For example, if the live region's aria-label
value is dynamically changing,
a screen reader automatically speak the changes.
Ensure that dynamic content changes to the live region are occurring within
the innerHTML of the live region.
Alert: Image Alt Not Used
Why did ANDI alert this?
This image has been declared presentational/decorative using
role=presentation
or role=none
but it has a non-empty alt
attribute.
Why is this an accessibility concern?
A screen reader will not speak the alt
text since it
sees the image as presentational or decorative.
What should be done?
If the image is truly decorative (non-meaningful) ensure that the output relating to this image is as expected.
Alert: Attribute Length Exceeds Character Limit
Why did ANDI alert this?
This element's
title
,
alt
, or
aria-label
attribute value has a length that exceeds 250 characters.
Why is this an accessibility concern?
An accessible name should be a concise identifier of an element. A screen reader has no way of skipping through sections of long accessible names. Shortening the accessible name will help with efficient page navigation using a screen reader.
What should be done?
If a long amount of text is needed, shorten the accessible name and use the
aria-describedby
attribute. The aria-describedby
provides a
screen reader user a way to make a selection to hear more information about
an element.
Alert: Ambiguous Link
Why did ANDI alert this?
This link shares an identical accessible name and accessible description as another link on the page, but the hrefs are different. Essentially, the links do not have descriptive text.
Why is this an accessibility concern?
Ambiguous links are a potential problem for all users, not just users of assistive technologies (screen readers). Because of this ambiguity (the name/description of the links are the same, but the destinations are different) a user may navigate to an unintended location.
Moreover, screen reader users have the capability to bring up a list of links by which they can efficiently navigate. If the links in such a list are not unique and "self-defining", then the accessibility of the page is affected.
What should be done?
If the href
s are different, the accessible name and accessible description of each link should be uniquely identified.
Note that, if the href
s are identical, the link names/descriptions can be the same or different.
Alert: Vague Link Text
Why did ANDI alert this?
The accessible name and description of this link is vague and does not provide a meaningful context.
Why is this an accessibility concern?
A person who is visually impaired may not be able to determine the full purpose of this link without seeking out its context in relation to nearby elements on the page.
What should be done?
Provide a meaningful accessible name/description for this link.
Alert: Link Click But No Keyboard Access
Why did ANDI alert this?
This link does not have an href
or tabindex
and a JavaScript click event was detected.
Why is this an accessibility concern?
This link performs some function but is not in the tab order. It may not be accessible to users who navigate using a keyboard.
What should be done?
Ensure that the ANDI Output is appropriate.
Close ANDI and test whether the link can be accessed using the tab key, shift+tab keys, arrow keys or other documented keys.
For a link to be in the keyboard tab order add
an href="#"
, or href="javascript:void(0)"
,
or tabindex="0"
.
If an href
is not being used it may be necessary to add
role="link"
to the
element so that a screen reader
will recognize the element as a link and include it in its Links List functionality.
Alert: Not Recognized As Link
Why did ANDI alert this?
This
element has a tabindex
but it does not have an href
.
Why is this an accessibility concern?
A screen reader may not identify this element as a link and the user may not know that the element is actionable.
What should be done?
Does this element function like a link? Click on it using a mouse. Navigate to it using the keyboard and press the enter key.
If the element performs a function, add role="link"
to the element or add an href
.
Doing so will ensure that the screen reader will identify the element as a link.
NOTE: If the element appears and operates like a button, add role="button"
and ensure that the element can be pressed using the space bar key.
If this element does not perform a function when clicked, this element might be an anchor target, in which case, disregard this alert.
Alert: Marquee Found
Why did ANDI alert this?
This element is a <marquee>
.
Why is this an accessibility concern?
A marquee, depending on its design, can cause flashing which can trigger seizures in some individuals. In addition, the constantly moving text within a marquee can be difficult to read for people with low vision or who have cognition disorders like dyslexia.
What should be done?
It is best to not use the <marquee>
tag and
to not allow any text to constantly move or scroll on the page.
Alert: Blink Found
Why did ANDI alert this?
This element is a <blink>
.
Why is this an accessibility concern?
This element can trigger seizures in some individuals when the content is large.
In addition, the blinking/flashing text within a <blink>
element
can be difficult to read for people with low vision
or who have cognition disorders like dyslexia.
What should be done?
Do not use the <blink>
tag and do not allow any text to repeatedly blink or flash on the page.
Alert: Server Side Image Map
Why did ANDI alert this?
This element contains a sever side image map.
Why is this an accessibility concern?
Server side image maps cannot be navigated by screen reader users and users who do not use a mouse.
What should be done?
Do not use server side image maps. Client side image maps are acceptable but must be made accessible
by adding alt
attributes to the <area>
tags.
Alert: Image Alt Not Descriptive
Why did ANDI alert this?
This image has alt
text that does not provide an equivalent text description conveying the purpose
and/or function of the image.
Why is this an accessibility concern?
If the image does not have a text alternative description that contains a meaningful representation of the image, then the image is not accessible to a person who is blind or visually impaired and uses a screen reader.
What should be done?
The image alt text or other Namer/Describer should provide a text alternative or brief description of the image.
Alternatively,
if the image is purely decorative and does not require an explanation,
add role=presentation
to the image or set the alt value to an empty string alt=""
.
Doing so will ensure that the screen reader does not try to describe the image.
Alert: Area Not In Map
Why did ANDI alert this?
ANDI has found an image map element, (<area>
),
that is not contained within a <map>
element.
What should be done?
To create a proper client-side image map, <area>
elements must be within a <map>
element.
Alert: Image Alt File Name
Why did ANDI alert this?
The image alt text contains a file name such as ".jpg", ".gif", ".png".
Why is this an accessibility concern?
If the image does not have a text alternative description that contains a meaningful representation of the image, then the image is not accessible to a person who is blind or visually impaired and uses a screen reader.
What should be done?
The image alt text or other Namer/Describer should provide a text alternative or brief description of the image.
Alternatively,
if the image is purely decorative and does not require an explanation,
add role=presentation
to the image or set the alt value to an empty string alt=""
.
Doing so will ensure that the screen reader does not try to describe the image.
Alert: Image Alt Redundant Phrase
Why did ANDI alert this?
The image alt contains a redundant phrase such as "image of ...", "photo of ...".
Why is this an accessibility concern?
A screen reader will automatically announce the word "graphic"
when an
tag is being used, therefore,
including the redundant phrase in the alt text increases verbosity.
What should be done?
Remove the redundant phrase from the alt
value.
Alert: Ensure Background Images Are Decorative
Why did ANDI alert this?
ANDI has found an element styled as a background-image
using CSS.
A manual evaluation of all background images is needed.
Why is this an accessibility concern?
When images contain important information, a person who is visually impaired will miss the important information if the image does not have a text description or text equivalent somewhere on the page.
Screen readers consider all background images to be decorative and therefore visually impaired users are not told about the presence of background images. Note: This is only an accessibility issue when background images contain important information.
What should be done?
Ensure that any background images that are meaningful have a text alternative somewhere on the page. Graphics/Images ANDI has two helpful features to locate background images: The Hide Background and Find Background buttons.
If meaningful background images are found with no text alternatives, consider these solutions:
-
Instead of using CSS to display the image, make the image inline by converting the element to a

tag and provide a text alternative for the image using thealt
attribute. This will make the image discoverable by screen reader users. -
Continue using CSS to display the background-image, but add
role="img"
to the element styled as a CSS background-image and provide an accessible name usingaria-label
oraria-labelledby
. This will make the image discoverable by screen reader users. - Provide a text description of the meaningful background image somewhere on the page.
Alert: Live Region Form Element
Why did ANDI alert this?
There is a "live region" on this page (aria-live
)
that contains a form element.
Why is this an accessibility concern?
Screen readers monitor live regions and will speak changes whenever the content of the live region changes.
If a form element is contained within the live region, the screen reader will be reading out the live region contents when the form element changes causing confusion and verbosity for screen reader users.
What should be done?
Remove form elements from the live region
or move the aria-live
to another element.
Alert: Live Region Not Container
Why did ANDI alert this?
This element is not a container element (cannot contain text or other elements)
and it is designated as a "live region" (aria-live
).
Why is this an accessibility concern?
Screen readers monitor live regions and will speak changes whenever the content of the live region changes. Since this element is not a container element and therefore has no contents, the design will not work as expected. i.e. screen readers will not recognize changes to this live region.
What should be done?
Only container elements (such as a

)
can be designated as live regions. Changes to the contents (innerText) of the
live region will trigger the screen reader to speak the changed content.
Alert: List Container Has Non-List Role
Why did ANDI alert this?
This list element

is contained by a
list container element

or

but the list container has a role that changes its semantics to
something that is not a list container.
Why is this an accessibility concern?
A screen reader will not recognize this as a list
because the semantics of the list container have been overridden with
a role
attribute.
What should be done?
Remove the role
from the list container,
or if it is necessary, move it to another containing element.
Alert: Aria-Level not Greater Than Zero Integer
Why did ANDI alert this?
The aria-level
attribute is not greater than zero and/or is not an integer.
Why is this an accessibility concern?
When the aria-level
on a role="heading"
element is not a greater than zero integer,
a screen reader will default the heading level to level 2.
What should be done?
Ensure that the aria-level
value is valid
and is an appropriate level for its location on the page.
Alert: Not Using Semantic Heading Markup
Why did ANDI alert this?
This element appears to be a false heading.
Why is this an accessibility concern?
Headings (text that is concise, has a large font size or bold font weight)
provide a way to visually organize and categorize sections of a page.
Users of assistive technology are able to quickly navigate web pages when headings exist on a page.
However, headings must be coded properly using semantic heading tags
(

through

)
in order for users of AT to navigate.
What should be done?
Convert this false heading, and any others on the page, into one of the semantic heading tags:

,
,
,
,
,

.
Alert: Conflicting Heading Level
Why did ANDI alert this?
This heading element's heading level implied by its tag name,
(

-

)
does not match the numeric aria-level
value.
Why is this an accessibility concern?
The intended heading level may not be communicated to users of assistive technology.
What should be done?
Always ensure that the heading level used is the proper
heading level in relation to the content and other headings on the page.
When role="heading"
is used, the
aria-level
will supersede the heading level from the tag name.
Therefore, either:
-
Only use native semantics: Remove
role="heading"
and thearia-level
from the element which will result in the level of the heading tag chosen. Doing so will resolve this alert. -
Use a generic element like

withrole="heading"
and thearia-level
instead of an

-

heading element. Doing so will resolve this alert. -
Disregard this alert and know that the
aria-level
supersedes the tag name's heading level.
As a best practice, stick with native semantics instead of ARIA whenever possible.
Alert: Heading Role No Aria-Level
Why did ANDI alert this?
This element was defined as a heading using role="heading"
but it was not given a heading level using aria-level
.
Why is this an accessibility concern?
A screen reader will assume the heading level to be level 2 since 2 is the default aria-level.
What should be done?
Use semantic HTML headings (

,

,

,

,

,

)
instead of role="heading"
or add the aria-level
attribute to the element and assign it a positive numeric value.
Alert: Label Would Increase Clickable Area
Why did ANDI alert this?
This radio button or checkbox does not have an associated
and
the size of the radio button or checkbox is less than 21px by 21px.
Why is this an accessibility concern?
People with motor disabilities who can used a mouse may have trouble clicking on a small target less than 21px by 21px. Note: This size limit (21px by 21px) is arbitrarily determined and not an official WCAG requirement.
What should be done?
Adding an associated
to a radio button or checkbox allows a mouse user
to click on the label to select the radio button or checkbox. This increases the size of the clickable area.
An associated
is also a standard way of providing an accessible name for a radio button or checkbox.
Alert: Content injected using CSS
Why did ANDI alert this?
This page has content injected using the CSS pseudo-elements ::before or ::after.
Why is this an accessibility concern?
Depending on the browser being used, Content injected using this technique may not recognized by screen readers, therefore, the text may not be communicated to individuals using assistive technologies. Specifically, in Internet Explorer screen readers will not detect recognize CSS pseudo-element content.
What should be done?
If the content is meaningful or important, it should be made apparent to a blind individual using a screen reader.
If the meaning of the injected content is available elsewhere on the page, no change is needed. Otherwise, remediation options are as follows:
- Abandon the CSS content injection technique and place text directly on the screen or use inline images.
- Properly name and describe elements with which the injected css content associates.
Alert: Element Has Background Image
Why did ANDI alert this?
This element is "on top of" a background-image, therefore, the contrast ratio cannot be automatically determined. The element background color could not be determined due to a background image.
Why is this an accessibility concern?
Informational text should have a contrast ratio that allows the text to be readable by people with moderately low vision.
What should be done?
Perform a manual contrast ratio test by selecting the primary color of the background image and the primary foreground color of the text using a color selector tool (Colour Contrast Analyser Installation).
The WCAG AA Contrast Ratio requirement is as follows:
- For Large Text (font-size of 18pt or font-size of 14pt and bold) a contrast ratio of at least 3:1
- Otherwise a contrast ratio of at least 4.5:1
- Logo or brand name text does not have to meet a contrast ratio requirement.
- Inactive (disabled) user interface components have no contrast requirement.
Alert: If Images Contain Text
Why did ANDI alert this?
The page contains inline images (
, <input[type='image']>
, or <svg>
).
Why is this an accessibility concern?
If an image contains informational text, that text should have a contrast ratio that allows the text to be readable by people with moderately low vision.
What should be done?
If the images on this page contain informational text, perform a manual contrast ratio test by selecting the primary background color and the primary foreground color of the text using a color selector tool (Colour Contrast Analyser Installation).
The WCAG AA Contrast Ratio requirement is as follows:
- For Large Text (font-size of 18pt or font-size of 14pt and bold) a contrast ratio of at least 3:1
- Otherwise a contrast ratio of at least 4.5:1
- Logo or brand name text does not have to meet a contrast ratio requirement.
Alert: Opacity Less Than 100%
Why did ANDI alert this?
This element has a CSS property opacity
with a value that is less than 1, thus making it semi-transparent.
Why is this an accessibility concern?
By reducing the opacity value to less than one, the element's foreground color and background color is affected and will lower the contrast ratio. Informational text should have a contrast ratio that allows the text to be readable by people with moderately low vision.
Is this really an issue? (disabled elements)
Sometimes developers use CSS opacity to make an element appear disabled.
Disabled elements do not need to be included in a contrast test,
but it is up to the tester to determine if the element is in a disabled state.
Moreover, to communicate to a screen reader user that an element is disabled,
the element should have aria-disabled="true"
.
What should be done?
If the text is not in a disabled state, perform a manual contrast ratio test by selecting the primary color of the background image and the primary foreground color of the text using a color selector tool (Colour Contrast Analyser Installation).
The WCAG AA Contrast Ratio requirement is as follows:
- For Large Text (font-size of 18pt or font-size of 14pt and bold) a contrast ratio of at least 3:1
- Otherwise a contrast ratio of at least 4.5:1
- Logo or brand name text does not have to meet a contrast ratio requirement.
Alert: Contrast ratio minimum requirement
Why did ANDI alert this?
This element has very low contrast between foreground and background colors. In other words, the background and foreground colors do not have a sufficient contrast ratio based on minimum requirements.
Why is this an accessibility concern?
Informational text should have a contrast ratio that allows the text to be readable by individuals with moderately low vision.
What should be done?
Adjust the text color and/or the background color of this element so that the contrast ratio is at or above the minimum required contrast ratio.
The WCAG AA Contrast Ratio requirement is as follows:
- For Large Text (font-size of 18pt or font-size of 14pt and bold) a contrast ratio of at least 3:1
- Otherwise a contrast ratio of at least 4.5:1
- Logo, brand name, and decorative text does not have to meet a contrast ratio requirement.
Alert: Disabled Elements Found
Why did ANDI alert this?
Disabled elements (disabled="disabled"
) were found on the page.
Why is this an accessibility concern?
Elements disabled using the disabled
attribute are not in the tab order by default
and cannot be placed in the tab order.
Therefore, a person who is visually impaired and using a keyboard to tab through the page
may not know that the field is disabled (or even exists on the page).
What should be done?
Some would argue that disabling elements is a bad design practice in general. Users may become confused or frustrated if they don't know why an element is disabled or how they can make it become enabled.
The disabling of an element does not always equate to an accessibility issue. However, an argument can be made that disabled elements violate some of the Four Principles of Accessibility. Namely, is the content Perceivable? Is it Operable? Is it Understandable?
There may be an opportunity to improve upon the design to make it more accessible and usable by everyone. Here are a few things to consider:
- Leave the elements disabled, but provide a description somewhere on the page letting users know that fields are disabled and why they are disabled or how to enable them if it's not intuitive.
- For native textbox elements, instead of using the
disabled
attribute, use thereadonly
attribute combined with CSS to make the element look disabled (grayed out). - Instead of using the
disabled
attribute, keep the element in the tab order, usearia-disabled="true"
, prevent the element from functioning using JavaScript, and modify CSS to make the element look disabled (grayed out). - Enable the element, and when the element is activated by the user, display a popup or notification letting the user know why the element cannot be used at this moment.
- Convert the element into screen text or a meaningful image with alternative text.
- Rather than display the element as disabled, remove the element entirely if it is not necessary to reduce user frustration with disabled elements.
Alert: Disabled Element Contrast
Why did ANDI alert this?
Disabled elements (disabled="disabled"
) were found on the page.
Disabled elements are inactive user interface components
and do not have color contrast requirements according to the
WCAG AA Contrast Ratio requirement.


Toggle navigation
Richie's FCC Pinterest Clone
Home
Login
ID:
Username:
Display Name:
Home
Upload
Logout


UPKAR MEADOWS OWNER'S ASSOCIATION
Upkar Meadows is a residential layout near electronic city, Bangalore. Its a very fast developing location with well connected roads and facilities. Very peaceful and clean environment srrounding the layout makes it an ideal place for dream home...
Amenities existing/Proposed at layout
Updates at layout


I'm Kay
A systems designer currently @ Microsoft. I've spent the last 10 years working at some of the worlds most loved brands.
Crafting products, envisioning experiences as well as architecting organizational wide design systems
View projects


|
Design Patterns - C++
|
#include <MeshIterator.h>
Public Member Functions | |
| MeshIterator (MeshCollection *) | |
| ~MeshIterator () | |
| int | Begin () |
| bool | End () |
| void | Next () |
| int | CurrentIndex () |
| Public Member Functions inherited from Iterator | |
| virtual | ~Iterator () |
|
explicit |
| MeshIterator::~MeshIterator | ( | ) |
|
virtual |
Implements Iterator.
|
virtual |
Implements Iterator.
|
virtual |
Implements Iterator.
|
virtual |
Implements Iterator.


Toggle navigation
TripPlanner
{{request.name}}
Accept
Accepted
Rejected
No new requests!
{{user.name}}
Logout
New Posts
My Trips
Tripsters
Friends


Man pleads not guilty to murder by reason of insanity
A 20-year-old man has pleaded not guilty to murdering a Japanese national in Dundalk nearly two years ago by reason of insanity.
Mohamed Morei, of no fixed abode, is charged with murdering Yosuke Sasaki, 24, at Long Avenue, Dundalk, Co Louth on 3 January, 2018.
Mr Morei, who is Egyptian, was in court to give his plea. He had the help of an interpreter for the arraignment proceedings.
A jury of seven men and five women was sworn in to hear the trial, which is due to begin tomorrow afternoon before Ms Justice Carmel Stewart and is expected to last up to two days.
Mr Justice Michael White told the jury that the facts of the offence are not in dispute and they would be summarised by Detective Inspector Martin Beggy of Dundalk Garda Station.
"The evidence in dispute is in relation to sanity and insanity," he said.
The judge informed the jury that two consultant forensic psychiatrists from the Central Mental Hospital will give evidence in the case.