Workplace and Digital Printing Solutions | Xerox

First time visit: View without clicking anything

Digital Printing Solutions for Production Print - Xerox

Workflow Software for Print Production - Xerox

Financial Services Solutions: RPA for Banks & Insurers - Xerox

Global Document Services - Xerox

Legal Workflow Solutions – IT, RPA & Print Services - Xerox

Education Workflow Solutions – IT, RPA & Print Services - Xerox

Xerox ConnectKey Technology: Mobile & Cloud Print Solutions

Workplace Apps - ConnectKey - Xerox

To comply with WCAG 2.1, fields must identify what their purpose is _programmatically_. If done correctly,
this allows browsers to help users fill in forms with known information, such as their name and email address.

This is accomplished via the `autocomplete` attribute, which should be set to a 
[supported value](https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete) wherever
appropriate, e.g. 

```html
<label for="name">
  First Name
</label>
<input id="name" type="text" autocomplete="given-name">
```

For fields where `autocomplete` is not appropriate, e.g. due to security, or the field not matching the
specification, the specific field should be ignored.

## Methodology

* All fields which could support `autocomplete` (e.g. text fields)
  are checked. Other fields - like dropdown menus - are ignored.
* The [accessible name](https://www.w3.org/TR/accname-1.2/) of each field is considered. In most cases this
  will be the `<label>` for the field.
* If the name matches a known pattern the field 
  must have an appropriate `autocomplete` value specified.
  For example, an `<input>` with type `text` with a label of 
  "First Name" would be expected to have an autocomplete value 
  of `given-name` or similar.

Note that using `autocomplete="on"` is not sufficient to pass this check, a
specific named autocomplete value must be used. See the
[supported values](https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/autocomplete).

## Troubleshooting

If a field is a false positive, check whether the field has an 
appropriate accessible name (i.e. a `<label>` or `aria-label`).

If the label is incorrect, Silktide may assume that the field 
requires `autocomplete` where it does not. You should fix the 
label to avoid this.

Otherwise, you can simply ignore the specific field.

## More information

* [How to use HTML 5.2 attributes](https://www.w3.org/WAI/WCAG21/Techniques/html/H98)

identify-input-purpose

December 2024

November 2024

Xerox

Title / URL	Issues
Workplace and Digital Printing Solutions \| Xeroxwww.xerox.com/en-us	6
First time visit: View without clicking anythingwww.xerox.com/en-us	6
Digital Printing Solutions for Production Print - Xeroxwww.xerox.com/en-us/digital-printing	5
Workflow Software for Print Production - Xeroxwww.xerox.com/en-us/digital-printing/workflow	5
Financial Services Solutions: RPA for Banks & Insurers - Xeroxwww.xerox.com/en-us/services/financial-solutions	4
Global Document Services - Xeroxwww.xerox.com/en-us/services	4
Legal Workflow Solutions – IT, RPA & Print Services - Xeroxwww.xerox.com/en-us/services/legal-solutions	4
Education Workflow Solutions – IT, RPA & Print Services - Xeroxwww.xerox.com/en-us/services/education-solutions	4
Xerox ConnectKey Technology: Mobile & Cloud Print Solutionswww.xerox.com/en-us/connectkey	3
Workplace Apps - ConnectKey - Xeroxwww.xerox.com/en-us/connectkey/workplace-apps	3

Identify the purpose of fields programmatically

Xerox

Where this issue has occurred