CTUS-9 - Last Name / First Name | Single Name

Owned by Derek Matthew
Last updated: Feb 25, 2021
4 min read

Add your comments directly to the page. Include links to any relevant research, data, or feedback.

Status

DONE

Impact

MEDIUM

Driver

@Derek Matthew 

Approver

 

Contributors

Digital Technology Services (@Derek Matthew, @Solomon Hsu , @David Kirolos )
Digital Communications (@Uni (Hwa Young) Oh @Michelle DaCruz (Unlicensed) @Don Sugden (Unlicensed) )
CXi (Robin.Sandhu@toronto.ca,Jennifer.Ma@toronto.cam @Jacqueline Tan (Unlicensed) )

Informed

 

Due date

Feb 13, 2020

Outcome

Feb 12, 2020

  • Initial design patterns narrowed down to two options

  • Final decision required as it relates

    • position of the checkbox

    • labels for (First Name, Last Name, Checkbox text)

    • any additional help text needed for each field

    • accessibility considerations

Feb 25, 2021

Documentation added to the Design Standards

Name (First Name, Last Name, Single Name)

Background

https://toronto.atlassian.net/browse/CTUS-9

Excerpt From the Common Data Elements Standard for City Forms

The updates to the Common Data Elements Standard for City Forms outlines the Information Management best practice approach to Single Name Identifiers.

Individuals who meet regulated criteria are now able to register a Single Name Identifier.

Until recently, Ontario's requirements for name registration only permitted dual names composed of at least one first name and a last name. This naming standard is a barrier to social inclusion for cultures with a single name tradition. Individuals registering a birth or requesting change of name certificate now can register a Single Name.

The City Clerk's Office establishes standards and practices for the collection and management of personal information, including name data. The best practice recommendation is that City forms and systems be designed to:

  • Treats single name as a unique data element, not as a type of first or last name;

  • Recognizes that name is now a data category with two subcategories: (a) "First

    Name, Last Name" and, (b) "Single Name"; and,

  • Informs form and system users that the "Single Name" subcategory should be used by persons with a legally-registered single name.

Relevant data

Options considered

Use the “@” to identify your comments and or feedback. If you want to add notes to the options considered please do so.

 

 

Options Selected For Testing

 

Option 1:

Option 2:

 

Option 1:

Option 2:

Description

 

 

Pros and cons & Other considerations

@Sara Greenwood Reading order is confusing. User might fill it in before seeing the checkbox and then have to re-type their name.

@Sara Greenwood Meets AODA compliance

@Sara Greenwood Logical reading order to see check box first

@Solomon Hsu When taking the WCAG 1.3.1 and 1.3.2 into consideration, this flow will be more ideal. Assistive Technologies like screen reader go through the elements from top to bottom. By hearing about the check box, users can expect that the elements immediately after have to do with the checkbox. Also, for magnifying application users, they may zoom in very closely. When they go through the contents, they can know if the “Single Name” condition applies to them while going through the content. Otherwise, they may take a guess and put their name into one of the first or last name fields. After that, they realize they could check the box for their conditions.

Notes:

@Sara Greenwood I feel like using a question is confusing - expected behaviour for a question would be answer “yes” or “no”. My text suggestion “I use a legally registered single name” or “check here if you use a legally registered single name”
@Michelle DaCruz (Unlicensed) I agree that a question is not necessary. “I use a legally registered single name” with a check box would work.

@Solomon Hsu We will need to add a status message to inform users about the name fields switching. This will be a more technical discussion that can come after the decision.

Action items

Outcome

  • Provide first name, last name fields with a checkbox that toggles the visibility of the single name field

    • The check box should use the following text: Check this box only if you have a Single Name on your Registered Birth Certificate or Change of Name Certificate (rather than a First Name and Last Name).

  • when the checkbox is selected the content entered into the first name and last name field are concatenated into the single name field

    • Example:

      • first name: “John”
        last name: “Smith”
        single name : “John Smith”

      • first name: “Plato“
        last name:””
        single name: “Plato”

  • If the first name & last name field is set to required, the single name field is set to required

  • If the first name & last name field is set to optional, the single name field is set to optional

  • Database/ Storage solutions must provide a separate field for first name, last name and single name