#docketing software | Explore Tumblr posts and blogs

pawborough · 2 years ago

Text

Hello all! Thanks for tuning into this month’s update! We’ve got a few things on the docket.

Asset Update - Snowfoots!

We’ve continued updating the cat assets to sport cleaner lines, better flipability, and match more in-line with our more recent illustrations.

It’s night and day with these guys! We’re thrilled to be giving them a fresh coat of paint.

The Guild - Preview Page

Leaders of a Guild will be able to import a custom emblem and edit the CSS boxes available! We’re so excited for this feature to help foster community storytelling and roleplay!

Want to play?

After trying it out for ourselves, we’re here to tell you all the battle mechanics as simply as possible, and give you the tools to try the combat system yourself with your friends!

If this is confusing and/or it’s your first time seeing or trying a game like this, we completely understand. By doing this, we are putting a lot of responsibility on you, the player, that would otherwise be on the software. We will try our best to supply pre-made components and a simple step-by-step instruction guide below.

If you want to try playing but still can’t understand everything, we recommend reaching out to a more experienced friend, or someone in our Discord, to help you out or play with you!

You need at least two people to play, and some dice! If you don’t have physical dice at home, try rolladie, or the Google dice roll function! Up to eight people can play with opposing teams of up to four!

Remember, if you’re playing with someone long distance, games are more fun if you’re faithful to the dice roll - no cheating!

Rules are below the cut!

If you’d like to build a character yourself, see the following steps:

Step 1: Roll for Statistics

You can do this by using dice to simulate how the software will choose your cat’s statistics. The software will have weighted outcomes for balance, and we simulate this with specific dice.

For this step, you will be rolling 2 12 sided dice (d12) and 1 6 sided die (d6). These outcomes will be your stat points. A statistic can have between 0-30 points.

You must roll these 3 dice 6 times, and record what number the dice equal to each time you roll.

If you get a 3 during one of your 6 rolls, you then must roll a four sided die (d4). This is to ensure it is possible to get 0-2. Count the following number for these rolls:

1 = 1 point

2 = 2 points

3 = 4 points

4 = 0 points

Your six roll numbers will fill in the following categories:

Roll 1 = Strength

Roll 2 = Sense

Roll 3 = Smarts

Roll 4 = Speed

Roll 5 = Savvy

Roll 6 = Stamina

Lastly, roll a 20 sided die (d20) and record the outcome 2 times. These rolls equal:

Roll 1 = Fortune

Roll 2 = Doom

Fill these numbers in the corresponding categories.

Now, count how many blocks you have for each category (excluding Stamina). These blocks are also known as dice or chances. Their official name is pending, but they equal the amount of times your cat has to succeed or fail for a single roll!

0 - 4 points = 1 die

5 - 9 points = 2 dice

10 - 14 points = 3 dice

15 - 19 points = 4 dice

20 - 24 points = 5 dice

25 - 29 points = 6 dice

30 points = 7 dice

Erase the dice you do not have from the sheet!

If you are playing at level 1, you are done.

However, if you wish to level up your cat to try the different battle mechanics, choose your class, then see the following:

Choose your class first.

After each level, you are given 10 stat points to distribute however you please among the 6 different statistical categories. This does not include Fortune and Doom.

For example, if you are going from level 1 to level 5, add 40 stat points to your character.

Add your stat points, then add the corresponding dice to the number your statistical category is at. Remember that the 6 categories all cannot go above 30.

Step 2: Choose a Class

Generally, your character’s class should depend on your statistics. The 5 classes are Warrior, Ranger, Medic, Thief, and Bard. Each class favors one of the statistical categories.

If your highest statistic is Strength, pick Warrior.

If your highest statistic is Sense, pick Ranger.

If your highest statistic is Smarts, pick Medic.

If your highest statistic is Speed, pick Thief.

If your highest statistic is Savvy, pick Bard.

If you have statistics that match in number, then pick whatever you like most of the two! If you’re playing with other people, it’s best that you do not have 2 of the same class on one team (a team equals 4 characters.) You may want to talk to the people you’re playing with to coordinate the classes of your teams.

However, this is just a guide. You can choose whatever class you please!

Step 3: Distribute Red and Green Dice

Depending on your class, certain statistical categories are poor or favored. Favored categories will have green dice, while poor categories will have red dice. Red and green dice are dice which give you guaranteed successes or critical successes, and red dice are dice which give your guaranteed failures or critical failures.

If this is confusing to you, that’s okay! It may make more sense when reading the combat outline. Simply follow the instructions:

If you are a Warrior, change 3 of your Sense dice to red, and 1 of your Strength dice to green.

If you are a Ranger, change 3 of your Strength dice to red, and 1 of your Sense dice to green.

If you are a Medic, change 3 of your Speed dice to red, and 1 of your Smarts dice to green.

If you are a Thief, change 3 of your Savvy dice to red, and 1 of your Speed dice to green.

If you are a Bard, change 3 of your Smarts dice to red, and 1 of your Savvy dice to green.

Note that if you do not have 3 dice to make red simply replace the amount of dice you have. For example, if you are a Thief with only 1 die in Savvy, then make that 1 die red!

If you are playing at level 1, you are done.

Otherwise, the amount of red and green dice you have in these categories will grow and shrink depending on level. See the following:

At level 1: Cats have 3 red dice in the poor statistic, and 1 green die in the favored statistic.

At level 3: Cats have 2 red die in the poor statistic, and 2 green die in the favored statistic.

At level 5: Cats have 1 red die in the poor statistic, and 3 green die in the favored statistic.

Class will also change to subclass once you are level 2 or above! See the next section for further details.

Step 4: Add Your Moves

If you are level 1, all 4 of your moves will already be planned for you. The moves you have are dependent on your class.

There are 5 basic move types:

Melee damage: Roll Strength for the number depleting the target’s stamina. Each success equals 1 point. Must be one tile apart, and the target must roll Speed for a chance to miss. Cannot hit diagonally.

Range damage: Roll Sense for the number depleting the target’s Stamina. Each success equals 1 point. Can hit up to six tiles apart between the two parties, cannot hit only 1 tile apart, and the target must roll Speed for a chance to miss. Can hit diagonally.

Dodge: Increases the amount or type of dice in the next Speed roll the user does.

Heal: Roll Smarts for the number added to the target’s stamina. Each success equals 1 point. Can hit diagonally.

Status: Affects the amount or type of dice for any and all rolls. Placement limitations depend on the move. Stackable over multiple turns.

Level 1 Warrior

Strike - Roll for Melee damage

Shield - Change 1 die to green during next Speed roll

Bandage - Roll for Stamina restoration of oneself

Warrior’s Spirit - Add +1 green die to next Strength roll

Level 1 Ranger

Longbow - Roll for Range damage

Dodge - Change 1 die to green during the next Speed roll

Bandage - Roll for Stamina restoration of oneself Ranger’s Spirit - Add +1 green die to next Sense roll

Level 1 Medic

Bite - Roll for Melee damage

Hiss - Roll for Range damage

First Aid - Roll for Stamina restoration of either oneself or a target. Must be 1 tile apart from the target.

Medic’s Spirit - Add +1 green die to next Smarts roll

Level 1 Thief

Slash - Roll for Melee damage

Dagger - Roll for Range damage

Hide - Change 1 die to green during the next Speed roll

Bandage - Roll for Stamina restoration of oneself

Level 1 Bard

Taunt - Roll for Melee damage

Shout - Roll for Range damage

Protection - Change 1 die to green during the next Speed roll

Bard’s Spirit - Add +1 white die to all rolls for one round to the target. Can be used on any target regardless of distance. Cannot be used on oneself

If you are playing at level 1, you are done!

If your character is level 2 or above, your character will need to choose a subclass.

Subclasses solely affect a single, special move called a submove. Each subclass has a single submove, so each cat will only ever have 1 submove. This move replaces one of the four you already have, and will grow in power for each level. Each class has 3 subclasses with 1 submove each.

Warrior Subclasses:

A. Warrior of the Fang

B. Warrior of the Claw

C. Warrior of the Body

Warrior Submoves:

A. Fangs - Melee damage +1 white die to the Strength roll at level 2 At level 3, +2 white dice At level 4, +3 white dice At level 5, +4 white dice Replaces the move Strike

B. Claws - Melee damage Damage affects all enemies within a 12 space radius at level 2 At level 3, radius is 24 At level 4, radius is 36 At level 5, radius is 48 Replaces the move Strike

C. Bodyguard - +1 white die to next Speed roll used to dodge an attack provided said attack is Melee At level 3, +2 white dice At level 4, +3 white dice At level 5, +4 white dice Replaces the move Shield

Ranger Subclasses:

A. Ranger of the Rain

B. Ranger of the Wind

C. Ranger of the Clouds

Ranger Submoves:

A. Multi-arrow - Range damage +1 white die to Sense roll at level 2 At level 3 +2 At level 4 +3 At level 5 +4 Replaces the move Longbow

B. Dash - Gives the user 9 spaces of movement for 3 rounds at level 2

2 spaces at level 3

16 spaces at level 4

20 spaces at level 5

Replaces the move Ranger’s Spirit

C. Safeguard - +1 white die to next Speed roll used to dodge an attack provided said attack is Range At level 3, +2 white dice At level 4, +3 white dice At level 5, +4 white dice Replaces the move Dodge

Medic Subclasses:

A. Medic of the Heart

B. Medic of the Mind

C. Medic of the Soul

Medic Submoves:

A. Healing Kiss - Roll for Stamina restoration of oneself or the target. Must be 1 tile apart +1 white die to smarts roll at level 2 +2 at level 3

+3 at level 4

+4 at level 5

Replaces the move First Aid

B. Hospital - Roll for Stamina restoration of oneself or all allies within a 12 space radius at level 2

At level 3, radius is 24

At level 4, radius is 36

At level 5, radius is 48

Replaces the move First Aid

C. Necromedic - Heal by bringing a fallen (Stamina fully depleted) ally back with 1/3rd Stamina, siphoning said Stamina from an enemy

At level 3, 1/2 total Stamina

At level 4, 2/3rd total Stamina

At level 5, 100% total Stamina

Cannot be used if an ally has not fallen during the combat instance. At each use, user takes damage equal to half of the damage siphoned and healed. Limited use of 4 times per mission. Has no range limit for target for target. Replaces the move First Aid

Thief subclasses:

A. Thief of Shadow

B. Thief of Time

C. Thief of Space

Thief Submoves:

A. Shadowsneak - Add (not replace) +1 green die to the next speed roll at level 2

+2 at level 3

+3 at level 4

+4 at level 5

Replaces the move Hide

B. Go-getter - Puts the user first in initiative order for the next 2 turns at level 2

3 turns at level 3

4 turns at level 4

5 turns at level 5

Replaces the move Hide

C. Two-step - Allows the user to choose whether to attack or move first, as opposed to move, then attack

Lasts for 2 turns at level 2

3 turns at level 3

4 turns at level 4

5 turns at level 5

Requires a speed success roll to activate. Replaces the move Hide

Bard Subclasses:

A. Bard of the Night

B. Bard of the Day

C. Bard of the Dawn

Bard Submoves:

A. Screech - At level 2, all enemies within a 12 space radius have 1 red die replaced in their next roll

At level 3, radius is 24 and 2 dice are replaced

At level 4, radius is 36 and 3 dice are replaced

At level 5, radius is 48 and 4 dice are replaced

Replaces the move Bard’s Spirit

B. Sing - At level 2, all allies within a 12 space radius have 1 green die replaced in their next roll

At level 3, radius is 24 and 2 dice are replaced

At level 4, radius is 36 and 3 dice are replaced

At level 5, radius is 48 and 4 dice are replaced

Replaces the move Bard’s Spirit

C. Deafen - At level 2, all red dice are changed to white during the next roll of all allies within a 12 space range, and all green dice are changed to white during the next roll of all enemies within a 12 space range

At level 3, radius is 24

At level 4, radius is 36

At level 5, radius is 48

Replaces the move Bard’s Spirit

The spirit status moves also grow with level if they are not replaced:

At level 1: Class’s Spirit does +1 color die to the designated roll

At level 3: Class’s Spirit does +2 color die to the designated roll

At level 5: Class’s Spirit does +3 color die to the designated roll

Once you have determined your character’s statistics. class, level, potential subclass, and moves, it’s now time to get your teams together and battle!

A single cat square takes up 4 spaces. It is recommended that you place your cats randomly on the board, and that you have as many allies as there are enemies. Meaning, if you have two cats on the A team, put two cats on the B team!

Turn order is decided by the cat with the highest Speed statistic among the group. If two cats are tied for Speed, then automatic green or red dice in the Speed stat are calculated (cats with a green die in the Speed stat will trump a cat without a green die, and cats with a red die will fall below a cat without a red die.) If the Speed stat is still a tie, roll a D6 to determine who is above the other within the tie. Remember, odd numbers are outcome A and even numbers are outcome B.

A turn in combat takes 2 parts:

1. Move

2. Attack

A turn must take place in this order, move then attack, unless a move has been used to designate otherwise.

Movement depends on level:

Level 1 cats may only move 6 spaces

Level 2 cats may only move 7 spaces

Level 3 cats may only move 8 spaces

Level 4 cats may only move 9 spaces

Level 5 cats may only move 10 spaces

You do not have to move the full amount of spaces, and you do not have to move at all if you do not want to!

For diagonal movement, count the spaces horizontally and vertically! You may not move nor attack 6 full spaces diagonally, but you may move 3 spaces to the side and 3 spaces up (this is not the case for Range attacks, which can hit diagonally without the use of slope!)

Attack consists of any of the moves at your cat’s disposal.

Every time a cat is hit with a Range or Melee attack, they must roll to avoid the attack. Cats must roll a number above or equal to the number of damage that they are being attacked for. If this number is not met, all the damage hits!

Remember to always roll for Fortune and Doom before rolling for the outcome!

This is done by using a 20 sided die, and counting the roll as a success if the number is under or equal to the Fortune or Doom statistic. For example, if your Fortune is 15, you need a 15 or below to succeed. If your Doom is 20, you will always succeed at a Doom roll.

If you succeed on Fortune, replace a white die in your roll with a green die! If you have only red and green dice, replace a red die! If you have only green dice, do nothing.

If you succeed on Doom, replace a white die in your roll with a red die! If you have only red and green dice, replace a green die! If you have only red dice, do nothing.

For every roll for outcome, use the amount of six-sided dice that the statistic calls for, with the necessary red and green dice accounted for. A die landing on an even number equals a success, and a die landing on an odd number equals a failure.

For calculating red, green, and white dice, keep the following in mind:

White fail: 0

White success: +1

Green fail: +1

Green success: +2

Red fail: 0

Red success: -2

If you end up with a negative number during your roll, your cat takes damage equal to the negative number. If a cat rolls to attack and ends with a -1 roll, said cat will take -1 damage instead.

Or, if a cat rolls to dodge an attack but ends with a -1 roll, that -1 will be added to the damage taken from the attack.

You must always use an attack to end your turn.

To finish off this briefing on how to play, here are some valuable notes on experience from one of the team members that we tested with!

“If you decide to play with other people, you may choose to have one person work as a GM* and do all the dice rolling and math in-game. Having several people do it themselves can get confusing. If you find yourself in this role, here are some tips.

*GM is a tabletop RPG term that usually stands for game master. (If you've heard of a dungeon master from dungeons and dragons, it's the same thing.) Usually the game master is in charge of controlling non-player characters and the overarching story. However, for this, it's a little different.

1. Colored Dice

If you are using physical dice, I cannot recommend enough to make sure that your d6s (6 sided dice) are red, green, and white (or at the very least 3 distinct colors.) Remembering which one is which when they're all the same is a headache and a half. If you're using an online roller, using 3 separate tabs all with the same dice to keep them separate should do the trick.

2. Enemy Cats

The way we played was 2 teams of 3 cats, each of us controlling a cat on either team. Personally I think this is the best way to play, as one finds themself less caught up in actually winning and more focused on having fun playing a silly game with friends. However, you are welcome to control your cats any number of ways. You could have the GM control all enemy cats and players control their own cat, you could have two people play two teams of opposing cats; whatever you have the most fun doing!

#3 Fortune and Doom

This is easy to forget in the beginning. Whenever ANY cat rolls dice for ANY reason you HAVE to roll for Fortune and Doom first. Have 2d20 (two twenty sided dice) that are green and red (or at least different colors) on hand at all times. It will become second nature to you by the end of the game. Attacking? F&D first. Dodging? F&D first. Healing? F&D first.

#4 Character Sheets

If your character sheets are on physical pieces of paper, it's most useful to have them displayed where you and their player can see. You will both need to check these sheets frequently, and needing to ask: "What's your fortune? How many strength dice do you have? What's your class again?" Becomes annoying for both parties.

#5 Roleplaying

This is totally optional, however I highly recommend it. Talking about how your cat is stricken with grief because their teammate died when they missed their last attack roll is half the fun. Give them backstories! Give them relationships! The world is your oyster.

Final notes:

I personally did not test tile functions and cats above level 1. I plan to in the future, but if you decide to play this, let us know how it goes! Please, please, PLEASE tell us everything that happened if you do this yourself. We want to know both the drama and what technical issues you ran into. Show no mercy in ripping different mechanics apart! This is how we learn! Thanks for reading! Have fun!”

Now, knock eachother out!

To Summarize: We shared the improved renders of the Snowfoot breed, a preview page of what Guilds will look like, and a breakdown of what we are testing so you can play for yourself!

What to expect next month: Continuation of asset and development production.

#kickstarter update

28 notes · View notes

imaginationofomi · 10 months ago

Text

Something Wicked This Way Comes

Chapter Eight

☪︎

Aubrie was sure her pacing had worn through at least two inches of the hospital's floor. She ignored direct orders, calling periodically for updates on Ellis' condition. He was unconscious for over a week, but she finally caught a break. Now awake and alert, she could question him about the night that he almost died.

She raced through the city and screeched into an empty spot in the parking lot. If it weren't for the receptionist reminding her that she needed a visitor's pass, she would've bypassed the desk completely, and her stop took extra time because she wasn't family.

Ellis refused to see anyone but his doctor, wife, or daughters. It took some convincing on her part and a flashing of her badge that nearly didn't get her anywhere because her title was not a detective nor was she accompanied by one. He'd been moved to a private wing of the hospital, long money affording him privileges more deserving people could use. The walls were painted a warm, burnt orange. He had a couch instead of the standard chairs, a cots for people that wanted to spent the night. Ellis, though drugged, showed visible signs of trauma and paranoia, eyes darting around the room when she walked in.

"Hello, Mr. Blackwell." She kept her voice soft to avoid startling him and stuck close to the doorway. Even in his hospital gown and covered with the sheet and blanket on the bed, she could tell that he'd lost some pounds since he was found. Smile lines deepened, the skin of his neck was beginning to droop, prominent wrinkles settled in the backs of his brown hands. She tried not to think about his injuries below the belt, "I'm Aubrie Parrish. I'm a forensic pathologist for the police department," she said, showing him her badge so he knew that she was the real deal.

"Pathologist? You're a coroner? I'm dead? I died? I'm dying? Is this Heaven?"

"No, sir, quite the opposite. I'm sure your doctor has shared how extensive your injuries were. You're a fighter." She thought about telling him just how close to death he was, how he'd already been pronounced when she arrived and had she not noticed that he was breathing, he would've bled out on that cold, cement floor. But revealing that information could open multiple people in the precinct to a lawsuit that she didn't want to be named in. She'd likely have to sit in court anyway for the biggest case in her docket. No way Mr. Serial Killer was going to come quietly or give a confession. There was a bigger plan at work, "I'm sorry about what happened to you. I wish I didn't have to disturb your recovery, but I need to know if you remember anything about the night you were attacked."

Ellis remained quiet, glancing at the blinds covering the window before he looked at his doctor, who stood quietly in the corner of the room to ensure their conversation was ethical. His large eyes drifted back to her, and he swallowed audibly, licking his chapped lips.

"Someone broke into my office," he said.

"Were the authorities alerted?"

"Whoever it was, they were good. They got past the alarm and my security." The man was visibly shaken. She didn't want to tell him that it might've been an inside job, but she had to. To get past a high tech alarm system AND guards? The person needed to have extensive knowledge of the building, the software, the walkthrough schedule, and access to their systems. It could've been someone that worked for him, and because they didn't succeed, she expected them to try again.

"Did you see who attacked you?"

"For a few seconds. They weren't alone. I think there was a woman. She tried to put me in a chokehold," he recalled, the memory obviously fuzzy judging from the confusion on his face.

"How sure are you that the second person was a woman?"

"I don't know, maybe 75 percent? They were wearing perfume, and they weren't very strong. The big one put a cloth over my nose and mouth because she couldn't hold onto me."

"How big?"

"Bigger than me. I only saw his eyes. He was wearing a plastic mask."

"What color were his eyes? Did you hear his voice at all? Did he say anything?"

"Blue, I think? They weren't speaking English."

Aubrie sighed quietly. He hadn't said anything useful in the few minutes she'd been there. Was it her line of questioning? She wasn't a detective, so she didn't know how to pull information out of live humans. The dead spoke to her. She was in new territory.

"The people that broke into your office, are they the ones that shot you?"

"The last thing I remember is passing out. I didn't know I'd been shot until I woke up here," he said, throwing her for a loop. He wasn't conscious when three holes were blasted into him, and his memory was limited. She wouldn't be getting a better description.

"Do you know why anyone would want to kill you, Mr. Blackwell?" she asked, hoping he didn't hear the frustration in her voice. It could very well deter him from being helpful then and in the future.

"I own multiple commercial properties and housing complexes. It could've been a tenant that got evicted, someone mad about rent hikes. I don't know. I keep my nose clean."

That was a lie. Money and connections kept him from doing time for the sex party that ended with two call girls deceased, but he was counting on her not knowing that. A lightbulb went off in Aubrie's head, widening her eyes and quickening her heartbeat. Money. Scandal. Death.

"Are you a member at Suite Surrender?" She meant to word the question in a way that wasn't so accusatory, but the possible connection made her rush the words out. Without verbally answering, Ellis' face gave him away, from the bug eyes to the nervous fidgeting in his hands and uptick in the heart monitor.

"I don't know what that is." Another lie.

"I can't help you if you don't tell me the truth, sir."

"I don't know what that is," he said again. She nodded slowly and backed toward the door. She'd gotten all she could out of him. His expression told her he wouldn't be sharing anything else, but she had a solid lead. Suite Surrender connected Bianca, Madison, and Ellis to each other. If she could connect Larissa to the business as well, Hughes wouldn't be able to deny the truth anymore, and she would have the full support of the department behind her.

"Okay. I'd advise you to find some people that you trust and keep a low profile for a while. Limit your contact with your employees. You weren't supposed to survive, but you did. Murderers don't like to leave loose ends untied."

"Hold on, you're saying they could come after me again?"

"It's a possibility," Aubrie answered, "The more information we have, the sooner we can get whoever it is off the streets. I'll leave my card in case you remember anything else. Thank you for your time, Mr. Blackwell. Get better soon." She turned and walked out of the room with the doctor behind her, facing him once they were away from the door, "I need the bullet that you pulled from his chest," she said to the man in the white lab coat.

"This way."

🂡🂡🂡

Suite Surrender was nothing if not inconspicuous. The adult resort sat at the edge of downtown, where the city met the beach. It was the first, or last depending on which direction one was driving, group of buildings on the hotel strip, but unless someone knew exactly what they were looking for, they would drive right past it. She had several times before she realized the unmarked building covered with vibrant vegetation was her destination for the afternoon.

There were thirteen structures in total, the epicenter of it all ten stories high with nothing but the lobby visible from the doors. Two men dressed in suits stood on either side of the gold revolving door. They wore shades, but their eyes were felt as she walked up.

"Authorized personnel only," the bigger of the guards said, using his arm to block her from the door.

"How do you know I'm not?"

"It's their job to know." A tall man appeared out of thin air. Cinnamon hair gelled and styled to perfection, his butterscotch skin glowed in the sun, amber eyes blinking at her with cool observation. His demeanor reminded her of Gio's. There was a quiet arrogance about him, like he knew he was desirable but untouchable, "Is there something I can help you with?"

"I called to make an appointment with the owner. The secretary gave me the run around."

"You don't make appointments with the owner here. He only sees who he needs to."

"Are you his right hand or something?" she asked, and his dark chuckle made an uncomfortable chill go down her spine.

"Or something," he replied and took a few daring steps in her direction. With him closer, she was forced to look up. She flinched at the sudden movement of his arm, glancing down at his outstretched hand, "Aubrie Parrish in the flesh." He waited for her to shake his hand. She took a step back instead.

"How do you know my name?"

"I know a lot about a lot of people. You included. Howard for undergrad, Duke for medical school, mom's local, dad lives in Sacramento with two wives and a husband. Your boyfriend's name is Bryce Hamilton, civil rights attorney. Girlfriend's name is Summer Wilde, metaphysics professor at BBCC. You're a forensic analyst for Briton Beach PD that doubles as a pathologist, and you frequent Sticky Fingers. I hope you know that place is child's play." He smirked at the bewildered look on her face, "What can I help you with, Aubrie? I won't ask again." It clicked for her then that the man speaking to her was exactly who she was looking for, but he intentionally avoided admitting it.

"I want to talk to the owner."

"He's a busy man, and he doesn't like to waste time." Stuffing his hands into the pockets of his slacks, he gave her some breathing room, but the smirk remained firm on his lips, "I'll relay whatever the message is."

"Bianca Cross is dead. So is Madison Torres," she spit out. His vibe was throwing her off, and the second the names came out of her mouth, the dangerously playful nature he displayed turned to stiffness, "And someone tried to kill Ellis Blackwell. This is the only place the three of them have in common. I need to talk to the owner."

"I'm not pleasant when I've been lied to." His voice deepened to a growl, and she gulped.

"I'm not lying. You already know I work for the police department. We found Bianca's body buried at the beach a couple of months ago. We found Madison not too long after in a warehouse. Someone is targeting people affiliated with this place, I'm sure of it. I need to know if Larissa Baldwin worked here."

"Inside. Now."

She took hurried steps to the door, thankful to be out from under the heat of the sun. The lobby was almost too quiet, only a few people roaming around. Empty chairs and couches decorated the luxury posh ground floor. A blonde and a brunette woman sat at the high reception desk, answering phones that rang almost as soon as they completed their call. She wondered which one she spoke to.

"Cancel the rest of my meetings," the man said without looking at either woman. He placed a huge hand on Aubrie's back and guided her to an elevator separate from the group next to the lobby. The lift had its own attendant who said nothing as he took them on a controlled trip to the top floor.

They were let out into a pristine office filled with warm tones of chocolate and wine. The lights were low, and two glances at the bookshelves revealed that they weren't just bookshelves. Some were lined with toys, erotic literature, candles, statues.

Aubrie expected someone to be waiting for them. It would be unsurprising if she was knocked out, dragged off to be held against her will. She was snooping where most people had the common sense not to snoop, but the man that knew too much about her took the seat behind his desk instead of rendering her unconscious.

"I should've known." She continued to play dumb, careful not to touch anything.

"Yes. You should've. Sit." He pointed to the empty couch adjacent to him, and a stare-off ensued until her ass was planted on the buttery cushion, "Tell me everything you know."

"I'm suppose to be the one asking questions," she said indignantly.

"You're not a detective, and you showed up on my property without a warrant. I don't have to tell you anything. Talk," he barked, making her shrink in her seat before she remembered who she was and straightened up.

"I don't have a lot to tell. I'm trying to find out what happened, and I feel like I'm the only one. No one is listening to me."

"How did Bianca die?"

Aubrie decided to keep some information to herself. She didn't even know the man's name. If he wasn't talking, neither was she.

"OD," she answered.

"I told you I don't like being lied to." He glared at her, and she began to sweat. His eyes were too intense, the forceful tone of his voice making her squirm inside.

"What makes you think I'm lying?"

"Bianca didn't do drugs. Anyone claiming she OD'ed is lazy and irresponsible. Are you lazy and irresponsible, Aubrie?"

"You tell me since you already know my life story."

His smirk was back but short-lived, "You're smarter than you like to let on. Let's be honest with each other. We'll get farther," he suggested.

"You first." Because she didn't know him from a can of paint, and she wasn't going to be left high and dry, "Larissa Baldwin. Did she work here?"

"She did. She quit several months ago. Are you telling me she's dead, too?"

"She is." Aubrie watched him put the pieces together. Stress lines took over his otherwise handsome face. She found something behind his head to focus on so she wouldn't drag her eyes up and down what she gathered was a very nice frame, "What can you tell me about her and Ellis Blackwell?"

"They were playmates. Ellis is a particular man with particular tastes. Larissa was the only one that never complained about him," the man said, "Do you have any leads? My most popular girls disappearing is bad for business."

"I'm here for a reason. This is my only lead. You're the closest I've gotten to knowing anything."

"What led you here?"

"Asking the right questions."

His smile was unnerving. He stood and crossed the room to a small bar. That was when she noticed the male bartender waiting for instructions.

"Do you drink?"

She was growing annoyed that she didn't know his name. He had her life typed out on a piece of paper somewhere, and she couldn't address him as anything other than sir. For some reason, she felt like he would get a kick out of that.

"Not while I'm working."

"You're off the clock today."

"Do you realize how creepy it is that you know this much about me?" she asked.

"I make it my business to know everything about anyone that harasses my secretaries to get in touch with me." His wrist twisted in a hand signal she didn't recognize, and the bartender moved, carefully placing two glasses on the counter and filling them with a dark liquid from a frosted glass decanter.

"At least you know I was harassing them for an important reason."

"Yes. I wish we were meeting under different circumstances. You're intriguing." He sat next to her, holding one glass out to her as he balanced the other on his knee and circled the rim of the glass with a fingertip, "What actually happened to Bianca? I've been honest with you. Your turn."

She took the glass from him but didn't sip, putting a careful distance between them. His office was designed for seduction, and it wasn't safe to fall into the trap of a good looking man with shady dealings. She didn't want to be the next one to end up without a pulse.

"Her autopsy was crazy. Official cause of death is blunt force trauma to the head. I'm positive she was kidnapped. She had ligature marks on her wrists and ankles, track marks. The blood in her left arm tested positive for fentanyl, but everywhere else was clean. The track marks on her wrist were braille. It spelled out Madam Psycho. Does that ring any bells for you?"

"It was one of her personas on the floor. This dick branded her?"

"Madison, too. Her's said Harlot's Race."

"And Larissa?"

"The Sacrificer."

A frown creased his face. He downed half of the liquid in his glass.

"What else do you know?"

"Does the name Robin Shank mean anything to you?"

"No. Who is he?"

"He was stalking Bianca before she disappeared. Listen, she was a friend of mine. I promised her parents justice, and my colleagues are bullshitting. I want this bitch handled," Aubrie said and got up.

"We want the same thing. Someone is fucking with me, and I don't appreciate it." He walked to his desk, pulled out a phone and placed it in her hand, "Keep it charged. There's only one number saved. Do not contact anyone else on this. You will call me if you find anything else. I'll get my people on the ground and keep you in the loop. You scratch my back, I scratch yours."

She went to the contacts to see the number, eyebrows lifting at the moniker.

"Your name is Cairo?"

"Make sure you keep that to yourself."

#black literature #black love #black fiction #polyamory #polyamorous #polyam #thriller #mystery #suspense

3 notes · View notes

phneltwrites · 1 year ago

Text

fic writer meme

I was tagged by @ziusik <3

1. how many works do you have on ao3?

between my two pseuds, 132. I started posting end of 2018 and i orphaned 1 fic so that's everything

2. what's your total ao3 wordcount?

996,548 words

3. what fandoms do you write for?

Right now various Thai BL, mostly offgun, and I'm on the docket for a DCU fic for a pal who won me in a raffle

4. what are your top 5 fics by kudos?

the top 17 of my most kudosed are all MDZS wangxian, what a powerful fandom (then a witcher then a leverage)

Love Is More Than Telling Me You Want It - the omegaverse big gender feels one

Yeah I Know How You Like It - wwx gets telepathy and lwj is horny then touching about it. love every time i get a comment on this that's like this is a pwp why am i crying. hehe

your persuasions - lwj has a big dick and wwx is a san francisco based high tech software programmer. they fuck about it

the earthquake in the room - alternate universe Canada modern university fic. In which lwj does not make wwx toast

wild for your skin - canonverse pwp

from this i suppose that most people are pretty disappointed when i update and it isn't smut

5. do you respond to comments?

always! I feel like fandom is this thing we're making together and when people reach out to me I reach back and in that way we both add stitches to the tapestry that is the community

6. what is the fic you wrote with the angstiest ending?

I think most of my fics have a hopeful ending. So it might be Verbs are a Tragedy the Captain Marvel Carol/Maria fic about Maria grieving. Or wait! maybe the Never Let Me Go fic because it ends right before you know that Chopper is about to get his heart broken. Or the John Wick fic about Helen cause you know she dies later and isn't able to keep her promise of helping John leave the business? Ok maybe I do have some angsty endings.

7. what's the fic you wrote with the happiest ending?

ha what is happy. Maybe the Leverage fic where Eliot has to pretend to be married to Hardison even though they are exes and that one ends with him proposing to Parker and Hardison and them being happy together

8. do you get hate on fics?

Rarely. Not usually hate at me but sometimes my fics make people pretty angry. I don't love it when people yell at the fic. the funniest though is getting an angry bookmark on a fic that i turned comments off of cause people were angry. like you do you in the bookmarks but lmao

9. do you write smut?

do i ever

10. do you write crossovers? what's the craziest one you have written?

I write fusions and crossovers! My wildest crossover is a 5x fic about Fezzik and Inigo from the princess bride meeting different other characters which actually might be the angstiest one now that I think about it because their last section is them going to the grey havens from lotr so they can sail into the west together. they also party with phryne fisher

11. have you ever had a fic stolen?

i think only onto wattpad

12. have you ever had a fic translated?

Yes, and it's so cool!

13. have you ever co-written a fic before?

Twice! One time on a leverage fic and it taught me how to use semi colons and also write introspection, a lesson i have forgotten and one time lesbian beach volleyball porn with a friend.

14. what's your all time favorite ship?

uhhhh oh no. they're all my favourites. of the ships i've written... no can't do it.

15. what is a WIP you want to finish but doubt you ever will?

I dream of finishing my pacific rim x avatar fusion with mdzs. the worldbuilding was so much fun.

Everything else I think I've comprehensively abandoned in drafts. rip carol and maria having fun in space, jon and tormund going to winterfell, and the shl ocean's 11 au oh shit also the fic where wwx was adopted into the nie sect and it changes very little in some ways. Otherwise I tend to finish things I'm kind of a robot

16. what are your writing strengths?

smut and extended metaphors

17. what are your writing weaknesses?

description, romance, tenses, character introspection. i also think my sentence level writing is not that strong

18. thoughts of writing dialogue in another language in fics?

do whatever you want forever

19. first fandom you wrote for?

leverage! my first fanfic is on ao3 for that show. though technically i did a creative writing exercise where nietzsche and the librarian from a Borges short story hooked up as a class assignment in university so idk i guess maybe literary rpf

20. favorite fic you have written?

uhhhhh. i genuinely don't know. they're all their own little thing. im more interested in hearing which of my fics are other people's faves

tagging @idrilka @defractum @daltoneering @giraffeter @ginnymoonbeam

#tag meme

11 notes · View notes

xneontragedyx · 1 year ago

Text

Skip to Table of Contents

U.S. flag

An official website of the United States government

Here’s how you know

Notice

The Public Right-of-Way Accessibility Guidelines (PROWAG) rulemaking has concluded. The PROWAG final rule has been published in the Federal Register. Please visit the Access Board’s PROWAG page for the guidelines.

USAB star logo

U.S. Access Board

Advancing Full Access and Inclusion for All

Information and Communication Technology

Revised 508 Standards and 255 Guidelines

PDF

About the ICT Accessibility 508 Standards and 255 Guidelines

These standards address access to information and communication technology (ICT) under Section 508 of the Rehabilitation Act and Section 255 of the Communications Act.

Section 508 of the Rehabilitation Act charges the Access Board with developing and promulgating this rule. The statute also charges the Access Board with providing Technical Assistance on Section 508, which is provided through webinars, trainings, and in close collaboration with GSA and materials available from Section508.gov.

Section 508 requires access to ICT developed, procured, maintained, or used by federal agencies. Examples include computers, telecommunications equipment, multifunction office machines such as copiers that also operate as printers, software, websites, information kiosks and transaction machines, and electronic documents. The Section 508 Standards, which are part of the Federal Acquisition Regulation, ensure access for people with physical, sensory, or cognitive disabilities.

The Section 255 Guidelines cover telecommunications equipment and customer-premises equipment — such as telephones, cell phones, routers, set-top boxes, and computers with modems, interconnected Voice over Internet Protocol products, and software integral to the operation of telecommunications function of such equipment.

Background

February 3, 1998 – The Board publishes the original Telecommunications Act Accessibility Guidelines.

December 21, 2000 – The Board issues the original Section 508 Standards.

July 6, 2006 – The Board organizes TEITAC, the Telecommunications and Electronic and Information Technology Advisory Committee, to assist in updating the Section 508 Standards and Telecommunications Act Guidelines.

April 3, 2008 – The Advisory Committee presents its final report to the Board.

March 22, 2010 – The Board releases a draft proposed rule for public comment, docket ATBCB-2010-0001.

December 8, 2011 – The Board issues a revised draft proposed rule for public comment, docket ATBCB-2011-0007.

February 27, 2015 – The Board ICT proposed rule for public comment, docket ATBCB-2015-0002.

January 18, 2017 – The Board issues the final rule, docket ATBCB-2015-0002-014.

January 22, 2018 – The Board issues correction to the final rule to restore provisions for TTY access, docket document ATBCB-2015-0002-0146.

Additional Resources

Section508.gov — GSA’s Government-wide IT Accessibility Program

Section 508 of the Rehabilitation Act (29 U.S.C. §794d)

Final Regulatory Impact Analysis (FRIA)

Comparison Table of WCAG 2.0 to Original 508 Standards

Mapping of WCAG 2.0 to Functional Performance Criteria

ICT Testing Baseline for Web Accessibility

Appendix A to Part 1194 – Section 508 of the Rehabilitation Act: Application and Scoping Requirements

508 Chapter 1: Application and Administration

E101 General

E101.1 Purpose

These Revised 508 Standards, which consist of 508 Chapters 1 and 2 (Appendix A), along with Chapters 3 through 7 (Appendix C), contain scoping and technical requirements for information and communication technology (ICT) to ensure accessibility and usability by individuals with disabilities. Compliance with these standards is mandatory for Federal agencies subject to Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d).

E101.2 Equivalent Facilitation

The use of an alternative design or technology that results in substantially equivalent or greater accessibility and usability by individuals with disabilities than would be provided by conformance to one or more of the requirements in Chapters 4 and 5 of the Revised 508 Standards is permitted. The functional performance criteria in Chapter 3 shall be used to determine whether substantially equivalent or greater accessibility and usability is provided to individuals with disabilities.

E101.3 Conventional Industry Tolerances

Dimensions are subject to conventional industry tolerances except where dimensions are stated as a range with specific minimum or maximum end points.

E101.4 Units of Measurement

Measurements are stated in metric and U.S. customary units. The values stated in each system (metric and U.S. customary units) may not be exact equivalents, and each system shall be used independently of the other.

E102 Referenced Standards

E102.1 Application

The specific editions of the standards listed in Chapter 7 are incorporated by reference into 508 Chapter 2 (Scoping Requirements) and Chapters 3 through 6 to the prescribed extent of each such reference. Where conflicts occur between the Revised 508 Standards and the referenced standards, these Revised 508 Standards apply.

E103 Definitions

E103.1 Terms Defined in Referenced Standards

Terms defined in referenced standards and not defined in E103.4 shall have the meaning as defined in the referenced standards.

E103.2 Undefined Terms

Any term not defined in E103.4 or in referenced standards shall be given its ordinarily accepted meaning in the sense that the context implies.

E103.3 Interchangeability

Words, terms, and phrases used in the singular include the plural and those used in the plural include the singular.

E103.4 Defined Terms

For the purpose of the Revised 508 Standards, the terms defined in E103.4 have the indicated meaning.

Agency

Any agency or department of the United States as defined in 44 U.S.C. 3502, and the United States Postal Service.

Alteration

A change to existing ICT that affects interoperability, the user interface, or access to information or data.

Application.

Software designed to perform, or to help the user to perform, a specific task or tasks.

Assistive Technology (AT)

Any item, piece of equipment, or product system, whether acquired commercially, modified, or customized, that is used to increase, maintain, or improve functional capabilities of individuals with disabilities.

Audio Description.

Narration added to the soundtrack to describe important visual details that cannot be understood from the main soundtrack alone. Audio description is a means to inform individuals who are blind or who have low vision about visual content essential for comprehension. Audio description of video provides information about actions, characters, scene changes, on-screen text, and other visual content. Audio description supplements the regular audio track of a program. Audio description is usually added during existing pauses in dialogue. Audio description is also called “video description” and “descriptive narration”.

Authoring Tool

Any software, or collection of software components, that can be used by authors, alone or collaboratively, to create or modify content for use by others, including other authors.

Closed Functionality

Characteristics that limit functionality or prevent a user from attaching or installing assistive technology. Examples of ICT with closed functionality are self-service machines, information kiosks, set-top boxes, fax machines, calculators, and computers that are locked down so that users may not adjust settings due to a policy such as Desktop Core Configuration.

Content

Electronic information and data, as well as the encoding that defines its structure, presentation, and interactions.

Document

Logically distinct assembly of content (such as a file, set of files, or streamed media) that: functions as a single entity rather than a collection; is not part of software; and does not include its own software to retrieve and present content for users. Examples of documents include, but are not limited to, letters, email messages, spreadsheets, presentations, podcasts, images, and movies.

Existing ICT

ICT that has been procured, maintained or used on or before January 18, 2018.

Hardware

A tangible device, equipment, or physical component of ICT, such as telephones, computers, multifunction copy machines, and keyboards.

Information Technology

Shall have the same meaning as the term “information technology” set forth in 40 U.S.C. 11101(6).

Information and Communication Technology (ICT)

Information technology and other equipment, systems, technologies, or processes, for which the principal function is the creation, manipulation, storage, display, receipt, or transmission of electronic data and information, as well as any associated content. Examples of ICT include, but are not limited to: computers and peripheral equipment; information kiosks and transaction machines; telecommunications equipment; customer premises equipment; multifunction office machines; software; applications; Web sites; videos; and, electronic documents.

Keyboard

A set of systematically arranged alphanumeric keys or a control that generates alphanumeric input by which a machine or device is operated. A keyboard includes tactilely discernible keys used in conjunction with the alphanumeric keys if their function maps to keys on the keyboard interfaces.

Label

Text, or a component with a text alternative, that is presented to a user to identify content. A label is presented to all users, whereas a name may be hidden and only exposed by assistive technology. In many cases, the name and the label are the same.

A set of selectable options.

Name

Text by which software can identify a component to the user. A name may be hidden and only exposed by assistive technology, whereas a label is presented to all users. In many cases, the label and the name are the same. Name is unrelated to the name attribute in HTML.

Non-Web Document

A document that is not: a Web page, embedded in a Web page, or used in the rendering or functioning of Web pages.

Non-Web Software

Software that is not: a Web page, not embedded in a Web page, and not used in the rendering or functioning of Web pages.

Operable Part

Hardware-based user controls for activating, deactivating, or adjusting ICT.

Platform Accessibility Services

Services provided by a platform enabling interoperability with assistive technology. Examples are Application Programming Interfaces (API) and the Document Object Model (DOM).

Platform Software

Software that interacts with hardware or provides services for other software. Platform software may run or host other software, and may isolate them from underlying software or hardware layers. A single software component may have both platform and non-platform aspects. Examples of platforms are: desktop operating systems; embedded operating systems, including mobile systems; Web browsers; plug-ins to Web browsers that render a particular media or format; and sets of components that allow other applications to execute, such as applications which support macros or scripting.

Programmatically Determinable

Ability to be determined by software from author-supplied data that is provided in a way that different user agents, including assistive technologies, can extract and present the information to users in different modalities.

Public Facing

Content made available by an agency to members of the general public. Examples include, but are not limited to, an agency Web site, blog post, or social media pages.

Real-Time Text (RTT)

Communications using the transmission of text by which characters are transmitted by a terminal as they are typed. Real-time text is used for conversational purposes. Real-time text also may be used in voicemail, interactive voice response systems, and other similar application.

Revised 508 Standards

The standards for ICT developed, procured, maintained, or used by agencies subject to Section 508 of the Rehabilitation Act as set forth in 508 Chapters 1 and 2 (36 CFR part 1194, Appendix A), and Chapters 3 through 7 (36 CFR part 1194, Appendix C).

Software

Programs, procedures, rules, and related data and documentation that direct the use and operation of ICT and instruct it to perform a given task or function. Software includes, but is not limited to, applications, non-Web software, and platform software.

Software Tools

Software for which the primary function is the development of other software. Software tools usually come in the form of an Integrated Development Environment (IDE) and are a suite of related products and utilities. Examples of IDEs include Microsoft® Visual Studio®, Apple® Xcode®, and Eclipse Foundation Eclipse®.

Telecommunications

The signal transmission, between or among points specified by the user, of information of the user’s choosing, without change in the form or content of the information as sent and received.

Terminal

Device or software with which the end user directly interacts and that provides the user interface. For some systems, the software that provides the user interface may reside on more than one device such as a telephone and a server.

Text

A sequence of characters that can be programmatically determined and that expresses something in human language.

TTY

Equipment that enables interactive text based communications through the transmission of frequency-shift-keying audio tones across the public switched telephone network. TTYs include devices for real-time text communications and voice and text intermixed communications. Examples of intermixed communications are voice carry over and hearing carry over. One example of a TTY is a computer with TTY emulating software and modem.

Variable Message Signs (VMS)

Non-interactive electronic signs with scrolling, streaming, or paging-down capability. An example of a VMS is an electronic message board at a transit station that displays the gate and time information associated with the next train arrival.

Voice over Internet Protocol (VoIP)

A technology that provides real-time voice communications. VoIP requires a broadband connection from the user’s location and customer premises equipment compatible with Internet protocol.

Web page

A non-embedded resource obtained from a single Universal Resource Identifier (URI) using HyperText Transfer Protocol (HTTP) plus any other resources that are provided for the rendering, retrieval, and presentation of content.

508 Chapter 2: Scoping Requirements

E201 Application

E201.1 Scope

ICT that is procured, developed, maintained, or used by agencies shall conform to the Revised 508 Standards.

E202 General Exceptions

E202.1 General

ICT shall be exempt from compliance with the Revised 508 Standards to the extent specified by E202.

E202.2 Legacy ICT

Any component or portion of existing ICT that complies with an earlier standard issued pursuant to Section 508 of the Rehabilitation Act of 1973, as amended (as republished in Appendix D), and that has not been altered on or after January 18, 2018, shall not be required to be modified to conform to the Revised 508 Standards.

E202.3 National Security Systems

The Revised 508 Standards do not apply to ICT operated by agencies as part of a national security system, as defined by 40 U.S.C. 11103(a).

E202.4 Federal Contracts

ICT acquired by a contractor incidental to a contract shall not be required to conform to the Revised 508 Standards.

E202.5 ICT Functions Located in Maintenance or Monitoring Spaces

Where status indicators and operable parts for ICT functions are located in spaces that are frequented only by service personnel for maintenance, repair, or occasional monitoring of equipment, such status indicators and operable parts shall not be required to conform to the Revised 508 Standards.

E202.6 Undue Burden or Fundamental Alteration

Where an agency determines in accordance with E202.6 that conformance to requirements in the Revised 508 Standards would impose an undue burden or would result in a fundamental alteration in the nature of the ICT, conformance shall be required only to the extent that it does not impose an undue burden, or result in a fundamental alteration in the nature of the ICT.

E202.6.1 Basis for a Determination of Undue Burden

In determining whether conformance to requirements in the Revised 508 Standards would impose an undue burden on the agency, the agency shall consider the extent to which conformance would impose significant difficulty or expense considering the agency resources available to the program or component for which the ICT is to be procured, developed, maintained, or used.

E202.6.2 Required Documentation

The responsible agency official shall document in writing the basis for determining that conformance to requirements in the Revised 508 Standards constitute an undue burden on the agency, or would result in a fundamental alteration in the nature of the ICT. The documentation shall include an explanation of why and to what extent compliance with applicable requirements would create an undue burden or result in a fundamental alteration in the nature of the ICT.

E202.6.3 Alternative Means

Where conformance to one or more requirements in the Revised 508 Standards imposes an undue burden or a fundamental alteration in the nature of the ICT, the agency shall provide individuals with disabilities access to and use of information and data by an alternative means that meets identified needs.

E202.7 Best Meets

Where ICT conforming to one or more requirements in the Revised 508 Standards is not commercially available, the agency shall procure the ICT that best meets the Revised 508 Standards consistent with the agency’s business needs.

E202.7.1 Required Documentation

The responsible agency official shall document in writing: (a) the non-availability of conforming ICT, including a description of market research performed and which provisions cannot be met, and (b) the basis for determining that the ICT to be procured best meets the requirements in the Revised 508 Standards consistent with the agency’s business needs.

E202.7.2 Alternative Means

Where ICT that fully conforms to the Revised 508 Standards is not commercially available, the agency shall provide individuals with disabilities access to and use of information and data by an alternative means that meets identified needs.

E203 Access to Functionality

E203.1 General

Agencies shall ensure that all functionality of ICT is accessible to and usable by individuals with disabilities, either directly or by supporting the use of assistive technology, and shall comply with E203. In providing access to all functionality of ICT, agencies shall ensure the following:

That Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees who are not individuals with disabilities; and

That members of the public with disabilities who are seeking information or data from a Federal agency have access to and use of information and data that is comparable to that provided to members of the public who are not individuals with disabilities.

E203.2 User Needs

When agencies procure, develop, maintain or use ICT they shall identify the needs of users with disabilities to determine:

How users with disabilities will perform the functions supported by the ICT; and

How the ICT will be developed, installed, configured, and maintained to support users with disabilities.

E204 Functional Performance Criteria

E204.1 General

Where the requirements in Chapters 4 and 5 do not address one or more functions of ICT, the functions not addressed shall conform to the Functional Performance Criteria specified in Chapter 3.

E205 Electronic Content

E205.1 General

Electronic content shall comply with E205.

E205.2 Public Facing

Electronic content that is public facing shall conform to the accessibility requirements specified in E205.4.

E205.3 Agency Official Communication

Electronic content that is not public facing shall conform to the accessibility requirements specified in E205.4 when such content constitutes official business and is communicated by an agency through one or more of the following:

An emergency notification;

An initial or final decision adjudicating an administrative claim or proceeding;

An internal or external program or policy announcement;

A notice of benefits, program eligibility, employment opportunity, or personnel action;

A formal acknowledgement of receipt;

A survey questionnaire;

A template or form;

Educational or training materials; or

Intranet content designed as a Web page.

EXCEPTION: Records maintained by the National Archives and Records Administration (NARA) pursuant to Federal recordkeeping statutes shall not be required to conform to the Revised 508 Standards unless public facing.

E205.4 Accessibility Standard

Electronic content shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

EXCEPTION: Non-Web documents shall not be required to conform to the following four WCAG 2.0 Success Criteria: 2.4.1 Bypass Blocks, 2.4.5 Multiple Ways, 3.2.3 Consistent Navigation, and 3.2.4 Consistent Identification.

E205.4.1 Word Substitution when Applying WCAG to Non-Web Documents

For non-Web documents, wherever the term “Web page” or “page” appears in WCAG 2.0 Level A and AA Success Criteria and Conformance Requirements, the term “document” shall be substituted for the terms “Web page” and “page”. In addition, in Success Criterion in 1.4.2, the phrase “in a document” shall be substituted for the phrase “on a Web page”.

E206 Hardware

E206.1 General

Where components of ICT are hardware and transmit information or have a user interface, such components shall conform to the requirements in Chapter 4.

E207 Software

E207.1 General

Where components of ICT are software and transmit information or have a user interface, such components shall conform to E207 and the requirements in Chapter 5.

EXCEPTION: Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to the requirements in Chapter 5.

E207.2 WCAG Conformance

User interface components, as well as the content of platforms and applications, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

EXCEPTIONS:

Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to E207.2.

Non-Web software shall not be required to conform to the following four Success Criteria in WCAG 2.0: 2.4.1 Bypass Blocks; 2.4.5 Multiple Ways; 3.2.3 Consistent Navigation; and 3.2.4 Consistent Identification.

Non-Web software shall not be required to conform to Conformance Requirement 3 Complete Processes in WCAG 2.0.

E207.2.1 Word Substitution when Applying WCAG to Non-Web Software

For non-Web software, wherever the term “Web page” or “page” appears in WCAG 2.0 Level A and AA Success Criteria and Conformance Requirements, the term “software” shall be substituted for the terms “Web page” and “page”. In addition, in Success Criterion in 1.4.2, the phrase “in software” shall be substituted for the phrase “on a Web page.”

E207.3 Complete Processes for Non-Web Software

Where non-Web software requires multiple steps to accomplish an activity, all software related to the activity to be accomplished shall conform to WCAG 2.0 as specified in E207.2.

E208 Support Documentation and Services

E208.1 General

Where an agency provides support documentation or services for ICT, such documentation and services shall conform to the requirements in Chapter 6.

Appendix B to Part 1194 – Section 255 of the Communications Act: Application and Scoping Requirements

255 Chapter 1: Application and Administration

C101 General

C101.1 Purpose

These Revised 255 Guidelines, which consist of 255 Chapters 1 and 2 (Appendix B), along with Chapters 3 through 7 (Appendix C), contain scoping and technical requirements for the design, development, and fabrication of telecommunications equipment and customer premises equipment, content, and support documentation and services, to ensure accessibility and usability by individuals with disabilities. These Revised 255 Guidelines are to be applied to the extent required by regulations issued by the Federal Communications Commission under Section 255 of the Communications Act of 1934, as amended (47 U.S.C. 255).

C101.2 Equivalent Facilitation

The use of an alternative design or technology that results in substantially equivalent or greater accessibility and usability by individuals with disabilities than would be provided by conformance to one or more of the requirements in Chapters 4 and 5 of the Revised 255 Guidelines is permitted. The functional performance criteria in Chapter 3 shall be used to determine whether substantially equivalent or greater accessibility and usability is provided to individuals with disabilities.

C101.3 Conventional Industry Tolerances

Dimensions are subject to conventional industry tolerances except where dimensions are stated as a range with specific minimum or maximum end points.

C101.4 Units of Measurement

C102 Referenced Standards

C102.1 Application

The specific editions of the standards listed in Chapter 7 are incorporated by reference into 255 Chapter 2 (Scoping Requirements) and Chapters 3 through 6 to the prescribed extent of each such reference. Where conflicts occur between the Revised 255 Guidelines and the referenced standards, these Revised 255 Guidelines apply.

C103 Definitions

C103.1 Terms Defined in Referenced Standards

Terms defined in referenced standards and not defined in C103.4 shall have the meaning as defined in the referenced standards.

C103.2 Undefined Terms

Any term not defined in C103.4 or in referenced standards shall be given its ordinarily accepted meaning in the sense that the context implies.

C103.3 Interchangeability

Words, terms, and phrases used in the singular include the plural and those used in the plural include the singular.

C103.4 Defined Terms

For the purpose of the Revised 255 Guidelines, the terms defined in C103.4 have the indicated meaning.

Application

Software designed to perform, or to help the user perform, a specific task or tasks.

Assistive Technology (AT)

Audio Description

Authoring Tool

Any software, or collection of software components, that can be used by authors, alone or collaboratively, to create or modify content for use by others, including other authors.

Closed Functionality

Characteristics that limit functionality or prevent a user from attaching or installing assistive technology.

Content

Electronic information and data, as well as the encoding that defines its structure, presentation, and interactions.

Customer Premises Equipment (CPE)

Equipment used on the premises of a person (other than a carrier) to originate, route, or terminate telecommunications service or interconnected VoIP service, including software integral to the operation of telecommunications function of such equipment. Examples of CPE are telephones, routers, switches, residential gateways, set-top boxes, fixed mobile convergence products, home networking adaptors and Internet access gateways which enable consumers to access communications service providers’ services and distribute them around their house via a Local Access Network (LAN).

Document

Hardware

A tangible device, equipment, or physical component of ICT, such as telephones, computers, multifunction copy machines, and keyboards.

Information and Communication Technology (ICT)

Keyboard

Label

Manufacturer

A final assembler of telecommunications equipment or customer premises equipment that sells such equipment to the public or to vendors that sell to the public.

A set of selectable options.

Name

Non-Web Document

A document that is not: a Web page, embedded in a Web page, or used in the rendering or functioning of Web pages.

Non-Web Software

Software that is not: a Web page, not embedded in a Web page, and not used in the rendering or functioning of Web pages.

Operable Part

Hardware-based user controls for activating, deactivating, or adjusting ICT.

Platform Accessibility Services

Services provided by a platform enabling interoperability with assistive technology. Examples are Application Programming Interfaces (API) and the Document Object Model (DOM).

Platform Software

Programmatically Determinable

Real-Time Text (RTT)

Revised 255 Guidelines

The guidelines for telecommunications equipment and customer premises equipment covered by Section 255 of the Communications Act as set forth in 255 Chapters 1 and 2 (36 CFR part 1194, Appendix B), and Chapters 3 through 7 (36 CFR part 1193, Appendix C).

Software

Software Tools

Specialized Customer Premises Equipment

Assistive technology used by individuals with disabilities to originate, route, or terminate telecommunications or interconnected VoIP service. Examples are TTYs and amplified telephones.

Telecommunications

The signal transmission between or among points specified by the user of information and of the user’s choosing without change in the form or content of the information as sent and received.

Telecommunications Equipment

Equipment, other than customer premises equipment, used by a carrier to provide telecommunications service or interconnected VoIP service and includes software integral to the operation of telecommunications function of such equipment.

Terminal

Text

A sequence of characters that can be programmatically determined and that expresses something in human language.

TTY

Variable Message Signs (VMS)

Voice over Internet Protocol (VoIP)

A technology that provides real-time voice communications. VoIP requires a broadband connection from the user’s location and customer premises equipment compatible with Internet protocol.

Web page

255 Chapter 2: Scoping Requirements

C201 Application

C201.1 Scope

Manufacturers shall comply with the requirements in the Revised 255 Guidelines applicable to telecommunications equipment and customer premises equipment (and related software integral to the operation of telecommunications functions) when newly released, upgraded, or substantially changed from an earlier version or model. Manufacturers shall also conform to the requirements in the Revised 255 Guidelines for support documentation and services, including electronic documents and Web-based product support.

C201.2. Readily Achievable

When a manufacturer determines that conformance to one or more requirements in Chapter 4 (Hardware) or Chapter 5 (Software) would not be readily achievable, it shall ensure that the equipment or software is compatible with existing peripheral devices or specialized customer premises equipment commonly used by individuals with disabilities to the extent readily achievable.

C201.3 Access to Functionality

Manufacturers shall ensure that telecommunications equipment and customer premises equipment is accessible to and usable by individuals with disabilities by providing direct access to all telecommunications functionality. Where manufacturers can demonstrate that it is not readily achievable for such equipment to provide direct access to all functionality, the equipment shall support the use of assistive technology and specialized customer premises equipment where readily achievable.

C201.4 Prohibited Reduction of Accessibility, Usability, and Compatibility

No change shall be undertaken that decreases, or has the effect of decreasing, the net accessibility, usability, or compatibility of telecommunications equipment or customer premises equipment.

EXCEPTION: Discontinuation of a product shall not be prohibited.

C201.5 Design, Development, and Fabrication

Manufacturers shall evaluate the accessibility, usability, and interoperability of telecommunications equipment and customer premises equipment during its product design, development, and fabrication.

C202 Functional Performance Criteria

C202.1 General

Where the requirements in Chapters 4 and 5 do not address one or more functions of telecommunications or customer premises equipment, the functions not addressed shall conform to the Functional Performance Criteria specified in Chapter 3.

C203 Electronic Content

C203.1 General

Electronic content that is integral to the use of telecommunications or customer premises equipment shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

C203.1.1 Word Substitution when Applying WCAG to Non-Web Documents

For non-Web documents, wherever the term “Web page” or “page” appears in WCAG 2.0 Level A and AA Success Criteria and Conformance Requirements, the term “document’ shall be substituted for the terms “Web page” and “page.” In addition, in Success Criterion in 1.4.2, the phrase “in a document” shall be substituted for the phrase “on a Web page.”

C204 Hardware

C204.1 General

Where components of telecommunications equipment and customer premises equipment are hardware, and transmit information or have a user interface, those components shall conform to applicable requirements in Chapter 4.

EXCEPTION: Components of telecommunications equipment and customer premises equipment shall not be required to conform to 402, 407.7, 407.8, 408, 412.8.4, and 415.

C205 Software

C205.1 General

Where software is integral to the use of telecommunications functions of telecommunications equipment or customer premises equipment and has a user interface, such software shall conform to C205 and applicable requirements in Chapter 5.

EXCEPTION: Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to the requirements in Chapter 5.

C205.2 WCAG Conformance

User interface components, as well as the content of platforms and applications shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

EXCEPTIONS:

Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to C205.2.

Non-Web software shall not be required to conform to Conformance Requirement 3 Complete Processes in WCAG 2.0.

C205.2.1 Word Substitution when Applying WCAG to Non-Web Software

For non-Web software, wherever the term “Web page” or “page” appears in WCAG 2.0 Level A and AA Success Criteria and Conformance Requirements, the term “software” shall be substituted for the terms “Web page” and “page.” In addition, in Success Criterion 1.4.2, the phrase “in software” shall be substituted for the phrase “on a Web page.”

C205.3 Complete Processes for Non-Web Software

Where non-Web software requires multiple steps to accomplish an activity, all software related to the activity to be accomplished shall conform to WCAG 2.0 as specified in C205.2.

C206 Support Documentation and Services

C206.1 General

Where support documentation and services are provided for telecommunications equipment and customer premises equipment, manufacturers shall ensure that such documentation and services conform to Chapter 6 and are made available upon request at no additional charge.

Appendix C to Part 1194 – Functional Performance Criteria and Technical Requirements

Chapter 3: Functional Performance Criteria

301 General

301.1 Scope

The requirements of Chapter 3 shall apply to ICT where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

302 Functional Performance Criteria

302.1 Without Vision

Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.

302.2 With Limited Vision

Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.

302.3 Without Perception of Color

Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.

302.4 Without Hearing

Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.

302.5 With Limited Hearing

Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing.

302.6 Without Speech

Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.

302.7 With Limited Manipulation

Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.

302.8 With Limited Reach and Strength

Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.

302.9 With Limited Language, Cognitive, and Learning Abilities

ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.

Chapter 4: Hardware

401 General

401.1 Scope

The requirements of Chapter 4 shall apply to ICT that is hardware where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

EXCEPTION: Hardware that is assistive technology shall not be required to conform to the requirements of this chapter.

402 Closed Functionality

402.1 General

ICT with closed functionality shall be operable without requiring the user to attach or install assistive technology other than personal headsets or other audio couplers, and shall conform to 402.

402.2 Speech-Output Enabled

ICT with a display screen shall be speech-output enabled for full and independent use by individuals with vision impairments.

EXCEPTIONS:

Variable message signs conforming to 402.5 shall not be required to be speech-output enabled.

Speech output shall not be required where ICT display screens only provide status indicators and those indicators conform to 409.

Where speech output cannot be supported due to constraints in available memory or processor capability, ICT shall be permitted to conform to 409 in lieu of 402.2.

Audible tones shall be permitted instead of speech output where the content of user input is not displayed as entered for security purposes, including, but not limited to, asterisks representing personal identification numbers.

Speech output shall not be required for: the machine location; date and time of transaction; customer account number; and the machine identifier or label.

Speech output shall not be required for advertisements and other similar information unless they convey information that can be used for the transaction being conducted.

402.2.1 Information Displayed On-Screen

Speech output shall be provided for all information displayed on-screen.

402.2.2 Transactional Outputs

Where transactional outputs are provided, the speech output shall audibly provide all information necessary to verify a transaction.

402.2.3 Speech Delivery Type and Coordination

Speech output shall be delivered through a mechanism that is readily available to all users, including, but not limited to, an industry standard connector or a telephone handset. Speech shall be recorded or digitized human, or synthesized. Speech output shall be coordinated with information displayed on the screen.

402.2.4 User Control

Speech output for any single function shall be automatically interrupted when a transaction is selected. Speech output shall be capable of being repeated and paused.

402.2.5 Braille Instructions

Where speech output is required by 402.2, braille instructions for initiating the speech mode of operation shall be provided. Braille shall be contracted and shall conform to 36 CFR part 1191, Appendix D, Section 703.3.1.

EXCEPTION: Devices for personal use shall not be required to conform to 402.2.5.

402.3 Volume

ICT that delivers sound, including speech output required by 402.2, shall provide volume control and output amplification conforming to 402.3.

EXCEPTION: ICT conforming to 412.2 shall not be required to conform to 402.3.

402.3.1 Private Listening

Where ICT provides private listening, it shall provide a mode of operation for controlling the volume. Where ICT delivers output by an audio transducer typically held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided.

402.3.2 Non-private Listening

Where ICT provides non-private listening, incremental volume control shall be provided with output amplification up to a level of at least 65 dB. A function shall be provided to automatically reset the volume to the default level after every use.

402.4 Characters on Display Screens

At least one mode of characters displayed on the screen shall be in a sans serif font. Where ICT does not provide a screen enlargement feature, characters shall be 3/16 inch (4.8 mm) high minimum based on the uppercase letter “I”. Characters shall contrast with their background with either light characters on a dark background or dark characters on a light background.

402.5 Characters on Variable Message Signs

Characters on variable message signs shall conform to section 703.7 Variable Message Signs of ICC A117.1-2009 (incorporated by reference, see 702.6.1).

403 Biometrics

403.1 General

Where provided, biometrics shall not be the only means for user identification or control.

EXCEPTION: Where at least two biometric options that use different biological characteristics are provided, ICT shall be permitted to use biometrics as the only means for user identification or control.

404 Preservation of Information Provided for Accessibility

404.1 General

ICT that transmits or converts information or communication shall not remove non-proprietary information provided for accessibility or shall restore it upon delivery.

405 Privacy

405.1 General

The same degree of privacy of input and output shall be provided to all individuals. When speech output required by 402.2 is enabled, the screen shall not blank automatically.

406 Standard Connections

406.1 General

Where data connections used for input and output are provided, at least one of each type of connection shall conform to industry standard non-proprietary formats.

407 Operable Parts

407.1 General

Where provided, operable parts used in the normal operation of ICT shall conform to 407.

407.2 Contrast

Where provided, keys and controls shall contrast visually from background surfaces. Characters and symbols shall contrast visually from background surfaces with either light characters or symbols on a dark background or dark characters or symbols on a light background.

407.3 Input Controls

At least one input control conforming to 407.3 shall be provided for each function.

EXCEPTION: Devices for personal use with input controls that are audibly discernable without activation and operable by touch shall not be required to conform to 407.3.

407.3.1 Tactilely Discernible

Input controls shall be operable by touch and tactilely discernible without activation.

407.3.2 Alphabetic Keys

Where provided, individual alphabetic keys shall be arranged in a QWERTY-based keyboard layout and the “F” and “J” keys shall be tactilely distinct from the other keys.

407.3.3 Numeric Keys

Where provided, numeric keys shall be arranged in a 12-key ascending or descending keypad layout. The number five key shall be tactilely distinct from the other keys. Where the ICT provides an alphabetic overlay on numeric keys, the relationships between letters and digits shall conform to ITU-T Recommendation E.161 (incorporated by reference, see 702.7.1).

407.4 Key Repeat

Where a keyboard with key repeat is provided, the delay before the key repeat feature is activated shall be fixed at, or adjustable to, 2 seconds minimum.

407.5 Timed Response

Where a timed response is required, the user shall be alerted visually, as well as by touch or sound, and shall be given the opportunity to indicate that more time is needed.

407.6 Operation

At least one mode of operation shall be operable with one hand and shall not require tight grasping, pinching, or twisting of the wrist. The force required to activate operable parts shall be 5 pounds (22.2 N) maximum.

407.7 Tickets, Fare Cards, and Keycards

Where tickets, fare cards, or keycards are provided, they shall have an orientation that is tactilely discernible if orientation is important to further use of the ticket, fare card, or keycard.

407.8 Reach Height and Depth

At least one of each type of operable part of stationary ICT shall be at a height conforming to 407.8.2 or 407.8.3 according to its position established by the vertical reference plane specified in 407.8.1 for a side reach or a forward reach. Operable parts used with speech output required by 402.2 shall not be the only type of operable part complying with 407.8 unless that part is the only operable part of its type.

407.8.1 Vertical Reference Plane

Operable parts shall be positioned for a side reach or a forward reach determined with respect to a vertical reference plane. The vertical reference plane shall be located in conformance to 407.8.2 or 407.8.3.

407.8.1.1 Vertical Plane for Side Reach

Where a side reach is provided, the vertical reference plane shall be 48 inches (1220 mm) long minimum.

graphical representation of dimensions for vertical plane side reach

407.8.1.2 Vertical Plane for Forward Reach

Where a forward reach is provided, the vertical reference plane shall be 30 inches (760 mm) long minimum.

graphical representation of dimensions for vertical plane forward reach

407.8.2 Side Reach

Operable parts of ICT providing a side reach shall conform to 407.8.2.1 or 407.8.2.2. The vertical reference plane shall be centered on the operable part and placed at the leading edge of the maximum protrusion of the ICT within the length of the vertical reference plane. Where a side reach requires a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum.

407.8.2.1 Unobstructed Side Reach

Where the operable part is located 10 inches (255 mm) or less beyond the vertical reference plane, the operable part shall be 48 inches (1220 mm) high maximum and 15 inches (380 mm) high minimum above the floor.

graphical representation of dimensions for unobstructed side reach

407.8.2.2 Obstructed Side Reach

Where the operable part is located more than 10 inches (255 mm), but not more than 24 inches (610 mm), beyond the vertical reference plane, the height of the operable part shall be 46 inches (1170 mm) high maximum and 15 inches (380 mm) high minimum above the floor. The operable part shall not be located more than 24 inches (610 mm) beyond the vertical reference plane.

graphical representation of dimensions for obstructed side reach

407.8.3 Forward Reach

Operable parts of ICT providing a forward reach shall conform to 407.8.3.1 or 407.8.3.2. The vertical reference plane shall be centered, and intersect with, the operable part. Where a forward reach allows a reach over a portion of the ICT, the height of that portion of the ICT shall be 34 inches (865 mm) maximum.

407.8.3.1 Unobstructed Forward Reach

Where the operable part is located at the leading edge of the maximum protrusion within the length of the vertical reference plane of the ICT, the operable part shall be 48 inches (1220 mm) high maximum and 15 inches (380 mm) high minimum above the floor.

graphical representation of dimensions for unobstructed forward reach

407.8.3.2 Obstructed Forward Reach

Where the operable part is located beyond the leading edge of the maximum protrusion within the length of the vertical reference plane, the operable part shall conform to 407.8.3.2. The maximum allowable forward reach to an operable part shall be 25 inches (635 mm).

graphical representation of dimensions for obstructed forward reach

407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach

The height of the operable part shall conform to Table 407.8.3.2.1.

Table 407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach Reach Depth Operable Part Height

Less than 20 inches (510 mm) 48 inches (1220 mm) maximum

20 inches (510 mm) to 25 inches (635 mm) 44 inches (1120 mm) maximum

graphical representation of dimensions for operable part height for obstructed forward reach

407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach

Knee and toe space under ICT shall be 27 inches (685 mm) high minimum, 25 inches (635 mm) deep maximum, and 30 inches (760 mm) wide minimum and shall be clear of obstructions.

graphical representation of dimensions for knee and toe space for obstructed forward reach

EXCEPTIONS:

Toe space shall be permitted to provide a clear height of 9 inches (230 mm) minimum above the floor and a clear depth of 6 inches (150 mm) maximum from the vertical reference plane toward the leading edge of the ICT.

graphical representation of dimensions for knee and toe space for obstructed forward reach exception one

At a depth of 6 inches (150 mm) maximum from the vertical reference plane toward the leading edge of the ICT, space between 9 inches (230 mm) and 27 inches (685 mm) minimum above the floor shall be permitted to reduce at a rate of 1 inch (25 mm) in depth for every 6 inches (150 mm) in height.

graphical representation of dimensions for knee and toe space for obstructed forward reach exception two

Supplemental graphic combining both Exceptions 1 and 2:

graphical representation of dimensions for knee and toe space for obstructed forward reach exceptions one and two

408 Display Screens

408.1 General

Where provided, display screens shall conform to 408.

408.2 Visibility

Where stationary ICT provides one or more display screens, at least one of each type of display screen shall be visible from a point located 40 inches (1015 mm) above the floor space where the display screen is viewed.

408.3 Flashing

Where ICT emits lights in flashes, there shall be no more than three flashes in any one-second period.

EXCEPTION: Flashes that do not exceed the general flash and red flash thresholds defined in WCAG 2.0 (incorporated by reference, see 702.10.1) are not required to conform to 408.3.

409 Status Indicators

409.1 General

Where provided, status indicators shall be discernible visually and by touch or sound.

410 Color Coding

410.1 General

Where provided, color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

411 Audible Signals

411.1 General

Where provided, audible signals or cues shall not be used as the only means of conveying information, indicating an action, or prompting a response

412 ICT with Two-Way Voice Communication

412.1 General

ICT that provides two-way voice communication shall conform to 412.

412.2 Volume Gain

ICT that provides two-way voice communication shall conform to 412.2.1 or 412.2.2.

412.2.1 Volume Gain for Wireline Telephones

Volume gain conforming to 47 CFR 68.317 shall be provided on analog and digital wireline telephones.

412.2.2 Volume Gain for Non-Wireline ICT

A method for increasing volume shall be provided for non-wireline ICT.

412.3 Interference Reduction and Magnetic Coupling

Where ICT delivers output by a handset or other type of audio transducer that is typically held up to the ear, ICT shall reduce interference with hearing technologies and provide a means for effective magnetic wireless coupling in conformance with 412.3.1 or 412.3.2.

412.3.1 Wireless Handsets

ICT in the form of wireless handsets shall conform to ANSI/IEEE C63.19-2011 (incorporated by reference, see 702.5.1).

412.3.2 Wireline Handsets

ICT in the form of wireline handsets, including cordless handsets, shall conform to TIA-1083-B (incorporated by reference, see702.9.1).

412.4 Digital Encoding of Speech

ICT in IP-based networks shall transmit and receive speech that is digitally encoded in the manner specified by ITU-T Recommendation G.722.2 (incorporated by reference, see 702.7.2) or IETF RFC 6716 (incorporated by reference, see 702.8.1).

412.5 Real-Time Text Functionality

[Reserved].

412.6 Caller ID

Where provided, caller identification and similar telecommunications functions shall be visible and audible.

412.7 Video Communication

Where ICT provides real-time video functionality, the quality of the video shall be sufficient to support communication using sign language.

412.8 Legacy TTY Support

ICT equipment or systems with two-way voice communication that do not themselves provide TTY functionality shall conform to 412.8.

412.8.1 TTY Connectability

ICT shall include a standard non-acoustic connection point for TTYs.

412.8.2 Voice and Hearing Carry Over

ICT shall provide a microphone capable of being turned on and off to allow the user to intermix speech with TTY use.

412.8.3 Signal Compatibility

ICT shall support all commonly used cross-manufacturer non-proprietary standard TTY signal protocols where the system interoperates with the Public Switched Telephone Network (PSTN).

412.8.4 Voice Mail and Other Messaging Systems

Where provided, voice mail, auto-attendant, interactive voice response, and caller identification systems shall be usable with a TTY.

413 Closed Caption Processing Technologies

413.1 General

Where ICT displays or processes video with synchronized audio, ICT shall provide closed caption processing technology that conforms to 413.1.1 or 413.1.2.

413.1.1 Decoding and Display of Closed Captions

Players and displays shall decode closed caption data and support display of captions.

413.1.2 Pass-Through of Closed Caption Data

Cabling and ancillary equipment shall pass through caption data.

414 Audio Description Processing Technologies

414.1 General

Where ICT displays or processes video with synchronized audio, ICT shall provide audio description processing technology conforming to 414.1.1 or 414.1.2.

414.1.1 Digital Television Tuners

Digital television tuners shall provide audio description processing that conforms to ATSC A/53 Digital Television Standard, Part 5 (2014) (incorporated by reference, see 702.2.1). Digital television tuners shall provide processing of audio description when encoded as a Visually Impaired (VI) associated audio service that is provided as a complete program mix containing audio description according to the ATSC A/53 standard.

414.1.2 Other ICT

ICT other than digital television tuners shall provide audio description processing.

415 User Controls for Captions and Audio Descriptions

415.1 General

Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 415.1.

EXCEPTION: Devices for personal use shall not be required to conform to 415.1 provided that captions and audio descriptions can be enabled through system-wide platform settings.

415.1.1 Caption Controls

Where ICT provides operable parts for volume control, ICT shall also provide operable parts for caption selection.

415.1.2 Audio Description Controls

Where ICT provides operable parts for program selection, ICT shall also provide operable parts for the selection of audio description.

Chapter 5: Software

501 General

501.1 Scope

The requirements of Chapter 5 shall apply to software where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

EXCEPTION: Where Web applications do not have access to platform accessibility services and do not include components that have access to platform accessibility services, they shall not be required to conform to 502 or 503 provided that they conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

502 Interoperability with Assistive Technology

502.1 General

Software shall interoperate with assistive technology and shall conform to 502.

EXCEPTION: ICT conforming to 402 shall not be required to conform to 502.

502.2 Documented Accessibility Features

Software with platform features defined in platform documentation as accessibility features shall conform to 502.2.

502.2.1 User Control of Accessibility Features

Platform software shall provide user control over platform features that are defined in the platform documentation as accessibility features.

502.2.2 No Disruption of Accessibility Features

Software shall not disrupt platform features that are defined in the platform documentation as accessibility features.

502.3 Accessibility Services

Platform software and software tools that are provided by the platform developer shall provide a documented set of accessibility services that support applications running on the platform to interoperate with assistive technology and shall conform to 502.3. Applications that are also platforms shall expose the underlying platform accessibility services or implement other documented accessibility services.

502.3.1 Object Information

The object role, state(s), properties, boundary, name, and description shall be programmatically determinable.

502.3.2 Modification of Object Information

States and properties that can be set by the user shall be capable of being set programmatically, including through assistive technology.

502.3.3 Row, Column, and Headers

If an object is in a data table, the occupied rows and columns, and any headers associated with those rows or columns, shall be programmatically determinable.

502.3.4 Values

Any current value(s), and any set or range of allowable values associated with an object, shall be programmatically determinable.

502.3.5 Modification of Values

Values that can be set by the user shall be capable of being set programmatically, including through assistive technology.

502.3.6 Label Relationships

Any relationship that a component has as a label for another component, or of being labeled by another component, shall be programmatically determinable.

502.3.7 Hierarchical Relationships

Any hierarchical (parent-child) relationship that a component has as a container for, or being contained by, another component shall be programmatically determinable.

502.3.8 Text

The content of text objects, text attributes, and the boundary of text rendered to the screen, shall be programmatically determinable.

502.3.9 Modification of Text

Text that can be set by the user shall be capable of being set programmatically, including through assistive technology.

502.3.10 List of Actions

A list of all actions that can be executed on an object shall be programmatically determinable.

502.3.11 Actions on Objects

Applications shall allow assistive technology to programmatically execute available actions on objects.

502.3.12 Focus Cursor

Applications shall expose information and mechanisms necessary to track focus, text insertion point, and selection attributes of user interface components.

502.3.13 Modification of Focus Cursor

Focus, text insertion point, and selection attributes that can be set by the user shall be capable of being set programmatically, including through the use of assistive technology.

502.3.14 Event Notification

Notification of events relevant to user interactions, including but not limited to, changes in the component’s state(s), value, name, description, or boundary, shall be available to assistive technology.

502.4 Platform Accessibility Features

Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) (incorporated by reference, see 702.4.1) listed below:

Section 9.3.3 Enable sequential entry of multiple (chorded) keystrokes;

Section 9.3.4 Provide adjustment of delay before key acceptance;

Section 9.3.5 Provide adjustment of same-key double-strike acceptance;

Section 10.6.7 Allow users to choose visual alternative for audio output;

Section 10.6.8 Synchronize audio equivalents for visual events;

Section 10.6.9 Provide speech output services; and

Section 10.7.1 Display any captions provided.

503 Applications

503.1 General

Applications shall conform to 503.

503.2 User Preferences

Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor.

EXCEPTION: Applications that are designed to be isolated from their underlying platform software, including Web applications, shall not be required to conform to 503.2.

503.3 Alternative User Interfaces

Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services.

503.4 User Controls for Captions and Audio Description

Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 503.4.

503.4.1 Caption Controls

Where user controls are provided for volume adjustment, ICT shall provide user controls for the selection of captions at the same menu level as the user controls for volume or program selection.

503.4.2 Audio Description Controls

Where user controls are provided for program selection, ICT shall provide user controls for the selection of audio descriptions at the same menu level as the user controls for volume or program selection.

504 Authoring Tools

504.1 General

Where an application is an authoring tool, the application shall conform to 504 to the extent that information required for accessibility is supported by the destination format.

504.2 Content Creation or Editing

Authoring tools shall provide a mode of operation to create or edit content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) for all supported features and, as applicable, to file formats supported by the authoring tool. Authoring tools shall permit authors the option of overriding information required for accessibility.

EXCEPTION: Authoring tools shall not be required to conform to 504.2 when used to directly edit plain text source code.

504.2.1 Preservation of Information Provided for Accessibility in Format Conversion

Authoring tools shall, when converting content from one format to another or saving content in multiple formats, preserve the information required for accessibility to the extent that the information is supported by the destination format.

504.2.2 PDF Export

Authoring tools capable of exporting PDF files that conform to ISO 32000-1:2008 (PDF 1.7) shall also be capable of exporting PDF files that conform to ANSI/AIIM/ISO 14289-1:2016 (PDF/UA-1) (incorporated by reference, see 702.3.1).

504.3 Prompts

Authoring tools shall provide a mode of operation that prompts authors to create content that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) for supported features and, as applicable, to file formats supported by the authoring tool.

504.4 Templates

Where templates are provided, templates allowing content creation that conforms to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1) shall be provided for a range of template uses for supported features and, as applicable, to file formats supported by the authoring tool.

Chapter 6: Support Documentation and Services

601 General

601.1 Scope

The technical requirements in Chapter 6 shall apply to ICT support documentation and services where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where otherwise referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

602 Support Documentation

602.1 General

Documentation that supports the use of ICT shall conform to 602.

602.2 Accessibility and Compatibility Features

Documentation shall list and explain how to use the accessibility and compatibility features required by Chapters 4 and 5. Documentation shall include accessibility features that are built-in and accessibility features that provide compatibility with assistive technology.

602.3 Electronic Support Documentation

Documentation in electronic format, including Web-based self-service support, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

602.4 Alternate Formats for Non-Electronic Support Documentation

Where support documentation is only provided in non-electronic formats, alternate formats usable by individuals with disabilities shall be provided upon request.

603 Support Services

603.1 General

ICT support services including, but not limited to, help desks, call centers, training services, and automated self-service technical support, shall conform to 603.

603.2 Information on Accessibility and Compatibility Features

ICT support services shall include information on the accessibility and compatibility features required by 602.2.

603.3 Accommodation of Communication Needs

Support services shall be provided directly to the user or through a referral to a point of contact. Such ICT support services shall accommodate the communication needs of individuals with disabilities.

Chapter 7: Referenced Standards

701 General

701.1 Scope

The standards referenced in Chapter 7 shall apply to ICT where required by 508 Chapter 2 (Scoping Requirements), 255 Chapter 2 (Scoping Requirements), and where referenced in any other chapter of the Revised 508 Standards or Revised 255 Guidelines.

702 Incorporation by Reference

702.1 Approved IBR Standards

The Director of the Office of the Federal Register has approved these standards for incorporation by reference into this part in accordance with 5 U.S.C. 552(a) and 1 CFR part 51. Copies of the referenced standards may be inspected at the U.S. Access Board, 1331 F Street, NW, Suite 1000, Washington, DC 20004, (202) 272-0080, and may also be obtained from the sources listed below. They are also available for inspection at the National Archives and Records Administration (NARA). For information on the availability of this material at NARA, call 202–741–6030 or go to National Archives Code of Federal Regulations Incorporation by Reference.

702.2 Advanced Television Systems Committee (ATSC)

Copies of the referenced standard may be obtained from the Advanced Television Systems Committee, 1776 K Street NW, Suite 200, Washington, DC 20006–2304.

702.2.1 ATSC A/53 Part 5:2014

Digital Television Standard, Part 5—AC-3 Audio System Characteristics, August 28, 2014.

IBR approved for Appendix C, Section 414.1.1.

702.3 Association for Information and Image Management (AIIM)

Copies of the referenced standard may be obtained from AIIM, 1100 Wayne Ave., Ste. 1100, Silver Spring, Maryland 20910.

702.3.1 ANSI/AIIM/ISO 14289-1-2016

Document Management Applications — Electronic Document File Format Enhancement for Accessibility — Part 1: Use of ISO 32000-1 (PDF/UA-1), ANSI-approved February 8, 2016.

IBR approved for Appendix C, Section 504.2.2.

702.4 Human Factors and Ergonomics Society (HFES)

Copies of the referenced standard may be obtained from the Human Factors and Ergonomics Society, P.O. Box 1369, Santa Monica, CA 90406–1369.

702.4.1 ANSI/HFES 200.2

IBR approved for Appendix C, Section 502.4.

702.5 Institute of Electrical and Electronics Engineers (IEEE)

Copies of the referenced standard may be obtained from the Institute of Electrical and Electronics Engineers, 10662 Los Vaqueros Circle, P.O. Box 3014, Los Alamitos, CA 90720–1264.

702.5.1 ANSI/IEEE C63.19-2011

American National Standard for Methods of Measurement of Compatibility between Wireless Communications Devices and Hearing Aids, May 27, 2011.

IBR approved for Appendix C, Section 412.3.1.

702.6 International Code Council (ICC)

Copies of the referenced standard may be obtained from ICC Publications, 4051 W. Flossmoor Road, Country Club Hills, IL 60478–5795.

702.6.1 ICC A117.1-2009

Accessible and Usable Buildings and Facilities, approved October 20, 2010.

IBR approved for Appendix C, Section 402.5.

702.7 International Telecommunications Union Telecommunications Standardization Sector (ITU-T)

Copies of the referenced standards may be obtained from the International Telecommunication Union, Telecommunications Standardization Sector, Place des Nations CH-1211, Geneva 20, Switzerland.

702.7.1 ITU-T Recommendation E.161

Series E. Overall Network Operation, Telephone Service, Service Operation and Human Factors—International operation - Numbering plan of the international telephone service, Arrangement of digits, letters and symbols on telephones and other devices that can be used for gaining access to a telephone network, February 2001.

IBR approved for Appendix C, Section 407.3.3.

702.7.2 ITU-T Recommendation G.722.2

Series G. Transmission Systems and Media, Digital Systems and Networks – Digital terminal equipment – Coding of analogue signals by methods other than PCM, Wideband coding of speech at around 16 kbit/s using Adaptive Multi-Rate Wideband (AMR-WB), July 2003.

IBR approved for Appendix C, Section 412.4.

702.8 Internet Engineering Task Force (IETF)

Copies of the referenced standard may be obtained from the Internet Engineering Task Force.

702.8.1 IETF RFC 6716

Definition of the Opus Codec, September 2012, J.M. Valin, Mozilla Corporation, K. Vos, Skype Technologies S.A., T. Terriberry, Mozilla Corporation.

IBR approved for Appendix C, Section 412.4.

702.9 Telecommunications Industry Association (TIA)

Copies of the referenced standard, published by the Telecommunications Industry Association, may be obtained from IHS Markit, 15 Inverness Way East, Englewood, CO 80112.

702.9.1 TIA-1083-B

Telecommunications—Communications Products—Handset Magnetic Measurement Procedures and Performance Requirements, October 2015.

IBR approved for Appendix C, Section 412.3.2.

702.10 Worldwide Web Consortium (W3C)

Copies of the referenced standard may be obtained from the W3C Web Accessibility Initiative, Massachusetts Institute of Technology, 32 Vassar Street, Room 32-G515, Cambridge, MA 02139.

702.10.1 WCAG 2.0

Web Content Accessibility Guidelines (WCAG) 2.0, W3C Recommendation, December 11, 2008.

IBR approved for: Appendix A (Section 508 of the Rehabilitation Act: Application and Scoping Requirements), Sections E205.4, E205.4 Exception, E205.4.1, E207.2, E207.2 Exception 2, E207.2 Exception 3, E207.2.1, E207.3; Appendix B (Section 255 of the Communications Act: Application and Scoping Requirements), C203.1, C203.1 Exception, C203.1.1, C205.2, C205.2 Exception 2, C205.2 Exception 3, C205.2.1, C205.3; and Appendix C (Functional Performance Criteria and Technical Requirements), 408.3 Exception, 501.1 Exception, 504.2, 504.3, 504.4, and 602.3.

Appendix D to Part 1194: Electronic and Information Technology Accessibility Standards as Originally Published on December 21, 2000

[65 FR 80523, Dec. 21, 2000. Redesignated and amended at 82 FR 5832, Jan. 18, 2017]

Subpart A — General

§ D1194.1 Purpose.

The purpose of this part is to implement section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. 794d). Section 508 requires that when Federal agencies develop, procure, maintain, or use electronic and information technology, Federal employees with disabilities have access to and use of information and data that is comparable to the access and use by Federal employees who are not individuals with disabilities, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities, unless an undue burden would be imposed on the agency.

§ D1194.2 Application.

(a) Products covered by this part shall comply with all applicable provisions of this part. When developing, procuring, maintaining, or using electronic and information technology, each agency shall ensure that the products comply with the applicable provisions of this part, unless an undue burden would be imposed on the agency.

(1) When compliance with the provisions of this part imposes an undue burden, agencies shall provide individuals with disabilities with the information and data involved by an alternative means of access that allows the individual to use the information and data.

(2) When procuring a product, if an agency determines that compliance with any provision of this part imposes an undue burden, the documentation by the agency supporting the procurement shall explain why, and to what extent, compliance with each such provision creates an undue burden.

(b) When procuring a product, each agency shall procure products which comply with the provisions in this part when such products are available in the commercial marketplace or when such products are developed in response to a Government solicitation. Agencies cannot claim a product as a whole is not commercially available because no product in the marketplace meets all the standards. If products are commercially available that meet some but not all of the standards, the agency must procure the product that best meets the standards.

(c) Except as provided by §1194.3(b), this part applies to electronic and information technology developed, procured, maintained, or used by agencies directly or used by a contractor under a contract with an agency which requires the use of such product, or requires the use, to a significant extent, of such product in the performance of a service or the furnishing of a product.

§ 1194.3 General exceptions.

(a) This part does not apply to any electronic and information technology operated by agencies, the function, operation, or use of which involves intelligence activities, cryptologic activities related to national security, command and control of military forces, equipment that is an integral part of a weapon or weapons system, or systems which are critical to the direct fulfillment of military or intelligence missions. Systems which are critical to the direct fulfillment of military or intelligence missions do not include a system that is to be used for routine administrative and business applications (including payroll, finance, logistics, and personnel management applications).

(b) This part does not apply to electronic and information technology that is acquired by a contractor incidental to a contract.

(c) Except as required to comply with the provisions in this part, this part does not require the installation of specific accessibility-related software or the attachment of an assistive technology device at a workstation of a Federal employee who is not an individual with a disability.

(d) When agencies provide access to the public to information or data through electronic and information technology, agencies are not required to make products owned by the agency available for access and use by individuals with disabilities at a location other than that where the electronic and information technology is provided to the public, or to purchase products for access and use by individuals with disabilities at a location other than that where the electronic and information technology is provided to the public.

(e) This part shall not be construed to require a fundamental alteration in the nature of a product or its components.

(f) Products located in spaces frequented only by service personnel for maintenance, repair, or occasional monitoring of equipment are not required to comply with this part.

§ D1194.4 Definitions.

The following definitions apply to this part:

Agency

Any Federal department or agency, including the United States Postal Service.

Alternate formats

Alternate formats usable by people with disabilities may include, but are not limited to, Braille, ASCII text, large print, recorded audio, and electronic formats that comply with this part.

Alternate methods

Different means of providing information, including product documentation, to people with disabilities. Alternate methods may include, but are not limited to, voice, fax, relay service, TTY, Internet posting, captioning, text-to-speech synthesis, and audio description.

Assistive technology

2 notes · View notes