text:
"Things Happen that are Too Big for You…": Writer/Director Kenneth Lonergan on the Director's Cut of his Masterpiece, Margaret
by Meredith Alloway
in Directors, Interviews, Screenwriters
Kenneth Lonergan, Margaret
Margaret may be one of the best movies you've never seen. It's the second film from writer/director Kenneth Lonergan, whose first, You Can Count On Me, won the Grand Jury Prize at Sundance in 2000, and third, Manchester by the Sea garnered two Academy Awards for Lead Actor and Original Screenplay. But Margaret suffered a different journey, shooting in 2005 and being released much later in 2011 for a very limited run — and a cut 36 minutes shorter than the one Lonergan preferred.
As part of its series, "The Way I See It: Directors' Cuts," the Quad in New York City screens the extended cut of the film this week, which runs over three hours long, so it feels an appropriate time to revisit what critics have called a "thwarted masterpiece." Were the constraints put on the film warranted, or did they keep it from a post-9/11 audience that would have greatly connected with its characters and appreciated its themes?
Margaret takes its name from the poem "Spring and Fall" by Gerard Manley Hopkins, and centers on a teenage girl named Lisa, played with vibrant vulnerability by Anna Paquin in her best role to date. Lisa is living in NYC with her actress mother Joan (Lonergan's real-life partner J. Smith-Cameron), when she is witness to a fatal bus accident. As much as Lisa tries to continue as normal, her life colored with other complex relationships, the incident becomes overwhelming and unavoidable. Lonergan weaves together a story that is as much about Lisa and her teenage troubles as it is about the lives of the New Yorkers around her and each ones' survival need to get something accomplished in a world that's self involved. It's the smaller scenes and behavioral moments in the film that inform the epic length but also add to the incredibly palatable, raw and profound texture of the piece.
We had a chance to talk to Lonergan about how he crafted Margaret, from the scripting phase to what actually occurred in the the tumultuous post production process. The parallels between the core story of the characters and the production journey of the film itself are evident. As Lonergan puts it, Lisa is "finding out that it's hard to get anything done since everyone else wants to get what they want done as well — just as much as you do." For many filmmakers, it's a battle they face with every project. Lonergan offers some wisdom on sticking to the truth of the story, while also satisfying demands and opinions that can feel as infinite as the art of cinema itself — and the "defeats" that come with it.
Filmmaker: I've always wondered about your writing process in general and especially with this film, given its scope. The original script ended up being 150 pages?
Lonergan: No, it was never that short! The first draft was very long but I never intended to shoot that much. When I was writing it, I tried to switch my mind off and just write, not edit at all. Normally when you're writing a script you think, okay, it's getting a little long, aim for somewhere between 100 to 125 pages. I decided to see what would happen if I didn't do that at all in the first draft. And for some reason, there was a lot to write about. The first draft ended up being something like 370 pages. The final shooting script was 168 pages — or 175 pages, depending on the formatting you use.
Filmmaker: I'm reading Stephen King's On Writing book right now —
Lonergan: Oh yeah, I have that. I haven't read it yet, but I just bought it over the summer.
Filmmaker: I have no idea what you will think about it, but he talks about just writing for your characters as opposed to writing plot. Plot will come through your characters. Is that something you thought about when you approached this?
Lonergan: I knew what the framework was, and I knew what the story was for the most part. For me, when I have the basic sequence of events in place, then I try to be pretty loose about what else might happen or what else might come up in the scenes. It's easy to let the story go wherever it wants when you have a framework.
Filmmaker: And that also allows for these amazing in-between and behavioral moments — it makes the film feel epic. In a lot of cinema now, we have the plot points: the car accident, the sobbing in the shower — but not these smaller scenes. I love the moment after the bus accident when Lisa comes back to her room and sits on the bed and she accidentally drips blood on the comforter. How do these behavioral specific scenes come about? Are they in the script, or do you discover them while you're shooting?
Lonergan: Most of it comes about in the script. Once you have actors and everybody else who's there to make the movie, of course other things come up all the time on the set. That scene, for instance, is scripted. I'm glad you liked it, I liked it too. The idea is that it's catching up with her, what just happened, and it's much more than she can handle, but she's still herself. She sits and then says, "Good one, Lisa," which is such a teenage thing to say about an imprint of a dead woman's blood on your bedspread. I can see why it makes her throw up — just the way people's feelings kick in at such odd intervals. Things happen that are too big for you, and it's so hard to process them and it's like your whole system is in revolt.
Filmmaker: Absolutely. And with that scene, it's shot like there's a hidden camera in her room — the only moment in the film where I noticed that choice.
Lonergan: Well, it's shot from above at a very severe diagonal angle, and we did two takes, I believe. The idea was to make you a little seasick, because that's what she's feeling. You're the first person who's mentioned that, but it does look a little like a security camera, and I didn't think of that. But it's apt, because the movie's looking in on her more than it's being told from her point of view.
Filmmaker: When I talk to some directors about the transition from the script to the shooting process, it's this whole metaphorical approach — how to bring themes in the script to life. As much as Margaret has a lot of big ideas embedded in the script, it sounds like your approach was very practical, one shot at a time.
Lonergan: Pretty much. I try to be guided by the feeling of the scene, not so much the meaning of the scene. The only thing I would say that got to a metaphorical level was the idea that Lisa's not necessarily the protagonist in her own story. We had a lot of discussions about this. I wanted the city to be a real presence in the film, not just in the shots of the city, but in the whole film. We discussed pretty early on the idea of shooting the movie as if she wasn't the main character. It was impossible to stay totally true to that, but the idea was there, and informed a lot of the shots and a lot of the way the scenes are choreographed. As much as possible, we tried to introduce other points of view, because that's one of the big things the movie is about. But, you know, hopefully the metaphorical level of that is in sync with the literal, on-the-ground telling of the story: she's finding out that it's hard to get anything done since everyone else wants to get what they want done as well — just as much as you do.
Filmmaker: Speaking of this, what actually happened in the six years, 2005 to 2011, it took to finish the film, as much as you can tell me?
Lonergan: Really, we need several hours for me to tell you everything that happened. It's a very long and not very interesting story. Basically, the shortest version I can think of is that the people who were paying for the film lost their confidence in my ability to finish the film on time, even though I assured them that I could. Then things got pretty hostile and they got adamant that I not show them any version that was not two-and-a-half hours long, which was the contracted length. But in most situations, there's an informal understanding that you can mess around with the length a little bit as long as the movie is going well. And because they had very little control over me, they clamped down on that, and I foolishly tried very hard to cram it into that. They basically wanted it to be two and a half hours and for me to be happy. Both of those things became impossible.
There's no way to tell this story quicker. We tried; it didn't work and fell apart. We did a pretty early cut which had a conventional approach and all the scenes were as short as possible, got in as late as possible, got out as early as possible, just like you're supposed to do in screenwriting school, and there was not enough narrative to sustain it.
Filmmaker: If you're trying to stick to the truth, is it just, throw length out the window? Is there an issue with the restraints of American cinema?
Lonergan: Well, I mean, at a certain point, everyone's got notes about what you're doing, and you have to listen to them because they're paying for it. That's completely different. Let's put it in a more friendly way. You show the movie to 10 friends, and they all have different thoughts on it. There's this constant interplay between needing a little help and someone to bounce things off of and needing to say, "No, no, you're right to hold that shot that long, it's not boring, it's really interesting." It's this funny interplay between the help you need from other people and then the help you really don't want from other people when you know what you're doing.
The other funny thing, I was thinking about at one point, when I was really lost — there are literally thousands of decisions to make, how in the world does anyone do it? And I thought, when Beethoven's writing a symphony, he can't possibly be thinking of it note by note. He hears something in his head and he writes it down, and then if he has a little trouble with the next part, he has to do some work and add a cue here. I don't mean to sound mystical about it, but you kind of hear the whole thing, or you have a feel for it, and if you lose your feel for it then you are forced to reconstruct it note by note and of course you're going to fuck it up.
Filmmaker: I did want to discuss the choice of music in your films. Nico Muhly's score in Margaret, coupled with classical music adds to this universal scope of the film — there's something about classical music as the tie that binds us all.
Lonergan: The starting point is just the kind of music that I like, that means something to me. In the case of Margaret, Nico himself said something really incredibly insightful about [Wagner's] Lohengrin: "It sounds like the music you like is not from her point of view, it's from higher up." That first time when Lisa's walking in slow motion and you hear that beautiful, beautiful Lohengrin, it's so cool because it's from her point of view because of the slow motion and the close ups, and suddenly [the film is] anthropological. You're looking at all these humans struggling, and you're out of her experience and in it at the same time. That particular piece was so rich in what it gave. It's so beautiful and so slow and sad and big. It just gives her teenage travails such a beautiful human and universal context.
Filmmaker: Manchester By the Sea and You Can Count On Me also deal with these people trying to find personal growth and some sort of catharsis after these awful tragedies. Lisa is holding a dying woman in her arms and the movie basically starts, which is normally not where a story begins. 2017 was such a shitty year, and we're all trying to find personal growth after tragedy. Do you think that's something we can do? Is that a question you ask yourself since you continue to write about it?
Lonergan: I think it's possible — that's a good question. All three films are interested in people who are grappling with things that are too big for them. In a certain way, political realities are not quite as big as that, hopefully, and they're a bit more in the nature of problems that can be — "solved," I think, is asking too much, but addressed in some way. So I don't quite put them in the same category as these big existential problems. In a way it would feel a bit defeatist to do that. On the other hand, when you get exhausted and you don't know what to do and things just seem too big and too awful to deal with, I guess that's where these particular stories come in. Lisa also has this incredible belief that she can wreak some kind of justice out of everyday indifference and normal life. This particular film is about how difficult it is to do that in the face of how much life there is to deal with, and how much other people want to do what they want to do. It's not really about the fact that everyone else is awful and she's right, but everyone else is busy pursuing their own ends. I think at the moment it feels like we're in something very big historically, but in terms of its universal scale, it feels like a bit of a smaller, more local struggle, which I hope isn't quite as difficult as the one she's grappling with. Although it may be.
Filmmaker: I do think it's a story that people connect with because everyone is trying to make a change, in whatever small demographic or bubble they're living in. You watch the film and think well, if she can do it, and she's like what, 17, 16, then hopefully there's hope for all of us.
Lonergan: She comes pretty close, but it doesn't quite work though. The very end of the story, through the defeat of her personal crusade, she's able to forgive her mother and have a bit more understanding for someone else. That's a positive note in the story. That relationship could go to pieces if she had more of a narrow mind. But she's able to understand that her mother is no worse than she is, through her attempts to do everything she could possibly do, while not listening to anybody. It's not just the story of someone who's defeated, but some who's defeated and forgives her mother for also being defeated.
Paul Mazursky Loves Talking To Women By Stacie Passon on Jan 14, 2013
Embodied Teaching By Holly Willis on Oct 20, 2016
Eastern Oregon Film Festival 2014 to Host Filmmaker Showcase By Nick Dawson on Jan 31, 2014


text:
TASCHINGER: Trump flip-flops on virus relief talks are hard to follow
Opinions // Editorials
Thomas Taschinger, Thomas Taschinger
Oct. 8, 2020 Updated: Oct. 8, 2020 12:49 p.m.
U.S. House Speaker Nancy Pelosi, a Democrat from California, center, speaks to members of the media as she walks to her office at the U.S. Capitol in Washington, D.C., U.S. on Thursday, Oct. 1, 2020. Talks Thursday between Pelosi and Treasury Secretary Steven Mnuchin brought no immediate breakthrough on a deal for a new pandemic relief package, while the House prepared to vote on a Democrat-only plan. Photographer: Stefani Reynolds/BloombergStefani Reynolds / Bloomberg
If you're confused by President Trump's ever-shifting position on a coronavirus economic relief package, you're not alone. In the past two days he has flip-flopped three separate times on this crucial issue at a time when the American people are looking for real answers on something very important to them.
Trump has said he likes to make these sudden and dramatic moves so people will think he's unpredictable. But this time he's just coming off as erratic — and possibly affected by his Covid medications. Joe Biden and Democratic senatorial candidates probably can't believe the early Christmas present that has been dropped into their laps.
Trump's original position, as noted in a typical all-caps Tweet on Saturday, was for Treasury Secretary Steven Mnuchin and House Speaker Nancy Pelosi to continue their negotiations on a followup to last spring's first package. That included help for small businesses, federal relief for the unemployed in the form of a $600 weekly supplement and a $1,200 stimulus check for everyone. As Trump put it:
"OUR GREAT USA WANTS & NEEDS STIMULUS. WORK TOGETHER AND GET IT DONE."
OK, a little over the top, but it basically reflected what he and other top Republicans had been saying for months, even if they and Democrats were not close together and didn't seem to be making progress.
All that changed Tuesday morning, when Trump rashly tweeted that he was ending the talks with the promise, "Immediately after I win, we will pass a major Stimulus Bill that focuses on hardworking Americans and small business."
It was a disastrous move — tactically, economically and politically — and the stock market plunged 375 points on Tuesday with the grim news. The president appeared to be missing out on a chance to jump-start the economy — and his faltering campaign for re-election.
But before you could call your stock brokers and tell them to sell anything they could, Trump flipped again. On Wednesday he abruptly tweeted:
10 occupations hit hardest by pandemic
1) Service workers
Percent laid off: 34
Percent reduced hours: 41
Percent reduced pay: 43
2) Arts, design and media workers
3) Small business owners
4) Construction or mining workers
5) Sales workers
6) Transportation workers
7) Manufacturing or production workers
8) Installation, maintenance or repair workers
9) Health care workers
10) Clerical or office workers
Source: AARP
"The House & Senate should IMMEDIATELY Approve 25 Billion Dollars for Airline Payroll Support, & 135 Billion Dollars for Paycheck Protection Program for Small Business. Both of these will be fully paid for with unused funds from the Cares Act. Have this money. I will sign now!"
Whew; I haven't been this confused since the final episode of "The Sopranos."
What probably happened is that panicky Republicans told Trump they would lose the Senate (and the presidency) if Trump dropped this ball so carelessly. Since that's one of the few thing that will motivate Trump, and because he has no problem zigging or zagging, he essentially went back to his original position — which is more talks.
There's still no guarantee the two parties will be able to hammer out a deal; they're far apart and the election is less than 30 days away. Basically, Republicans have suddenly remembered they're the party of fiscal responsibility and want to cap the new package at $1 trillion (in borrowed money, of course) while Democrats wanted more (of course), as much as $2 trillion.
Even if the discussion doesn't go anywhere, savvy Republicans like Senate Majority Leader Mitch McConnell realize that there's no harm in talking. If the negotiations collapse, both sides could and would blame the other for being unreasonable.
But voters should be hoping that doesn't happen, because the U.S. economy really needs a shot in the arm. Even conservatives are saying that it makes much more sense to inject some money into the system now to speed up the recovery instead of having the downturn linger for the rest of this year and into 2021. Some economists worry about a double-dip recession without a relief package.
Trump still thinks he will win his re-election race, though the polls are showing a large and growing double-digit lead for Joe Biden.
If those polls are accurate and no agreement is reached, President-elect Biden will have a chance to hammer out an early deal with Congress (especially if Republicans lose the Senate). He will then be able to claim justifiable credit for getting an important job done while Trump only talked about it. This would allow Biden to shape the recovery just about any way he wants, though for better or worse he will own it anyway.
I guess we'll just watch the bouncing ball and find out if the reasonable compromise in Washington is as dead as it looks. Let's just hope that when a package is finally agreed upon, this year or next, we haven't dug ourselves into too deep of a hole by then.
TTaschinger@BeaumontEnterprise.com
Thomas Taschinger
Thomas Taschinger is the opinions editor for the Beaumont Enterprise.

redpajama_set_name: RedPajamaCommonCrawl


text:
@implementation TVCResponse

-(id) initWithAuthor:(TVCPlayer *)author andMessage:(NSString *)message {
    self = [super init];
    if(self) {
        self.author = author;
        self.message = message;
    }
    return self;
}

@end

redpajama_set_name: RedPajamaGithub


text:
Usually, "comic book" is a term of derision as far as films are concerned. In this case, though, the source material is Alan Moore's excellent graphic novel, so it'd be more of a complement. Which means we're going to have to find a new term of derision, because the film is appalling. To be fair, I was watching it on a nine inch screen in the back of the seat in front of me, and the tape kept jumping, so I probably didn't get as much from the special effects as I would've done on the big screen, but this just meant that I paid more attention to the script. Oh, the script...
The original graphic novel was multi-layered, intelligent, and the characterization was superb. The film version has none of this; the dialogue rarely rises above merely functional, serving to bridge between one explosion and the next, and at its worst vying with whichever Batman sequel had Mr Freeze in it ("Batman! There's a new villain attacking the museum!"). The story had been almost entirely replaced, which wouldn't necessarily be a bad thing, if the new one wasn't so nonsensical. And the characters have been cut to ribbons. Whereas, for example, Alain Quatermain was, in the comics, a washed-up opium addict, he's been cleaned up for the film, and given a dead son to make up for the morphine. Hyde is reduced to a misunderstood lunk, and the invisible man becomes a mockney thief, straight out of Carry On Up The Twightlight Zone.
The one improvement over the original comes in the form of Dorian Grey, played by Stuart Townsend (of Shooting Fish fame; anyone who knew me as an undergraduate could tell you I'm slightly partial to said film). He has all the best lines, and steals the screen whenever he's on it. This is a marked contrast to Tom Sawyer, who, while not actually bad in any particular way, is entirely superfluous. A marksmen? We've already got Quatermain. A substitute son for the latter? A needle would've been better. Love interest for Mina? Dorian blows him out of the water. About his only contribution is that he's an American in what is otherwise an almost exclusively European League (with the exception of Nemo, who has remained Indian, although he has mysteriously gained Kung Fu).
In all fairness, LXG (as Twentieth Century Fox are encouraging people to refer to it) doesn't nearly approach the nadir of last summer (Head and Shoulders, anyone?), but I was expecting so much more. The concept is intriguing, and the comic is superb. Unfortunately, the film doesn't live up to this.
Argh! My Life Points!


Now there's a wedding to remember. Jamie and Mark Phillips knew they were going to have a baby, so they wanted to be married before the baby was born. The baby had other plans. As Jamie walked down the aisle, she started to feel contractions, and when sitting down to dinner, her water broke. Everybody says she's the first one to arrive at the hospital to give birth while still wearing a wedding dress and veil.
Well, hopefully daddy dearest will have a little easier time remembering their anniversary.


Contemporary 4* accommodation with a delicious breakfast in our award winning terrace restaurant overlooking our private, manicured gardens.
Our Azure Leisure Club boasts a 20 metre pool, separate children's pool, sauna, steam room and fully equipped gymnasium. The Azure Beauty Rooms offers a wide range of relaxing treatments for both male and females.
Escape for 1 Night Bed & Breakfast and enjoy a sumptuous Dinner in our award winning Terrace Restaurant.
Escape for 2 Nights Bed & Breakfast and enjoy Dinner on an evening of your choice in the award winning Terrace Restaurant.


WordPress has been updated to version 4.9.8 a security and maintenance release.
WordPress has been updated to version 4.9.7 a security and maintenance release.
People have been requesting this for some time, so introducing an all new plugin coming from the good people of NextScripts. Read here to find out more.
Pinterest, Instagram, and Flickr have been added to the Collab theme, theme options.
The Iso Shortcode has been released for all to use.
The update inhibits an infinite loop from occurring.


text:
[contents] [guidelines]
WD-WAI-USERAGENT-TECH-19980309
Techniques for User Agent Accessibility Guidelines
W3C Working Draft 9-Mar-1999
http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990309/wai-useragent-tech
http://www.w3.org/WAI/UA/WD-WAI-USERAGENT/wai-useragent-tech
Latest public version:
http://www.w3.org/TR/WD-WAI-USERAGENT/wai-useragent-tech
Previous version:
Latest "User Agent Accessibility Guidelines":
http://www.w3.org/WAI/UA/WD-WAI-USERAGENT
Latest public version of "User Agent Accessibility Guidelines":
http://www.w3.org/TR/WD-WAI-USERAGENT
Jon Gunderson <jongund@uiuc.edu>
Ian Jacobs <ij@w3.org>
Copyright © 1999 W3C (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.
This document describes techniques that user agent developers may use to satisfy the checkpoints listed in "User Agent Accessibility Guidelines." Techniques relate to the accessibility of user interfaces, content rendering, program interfaces, and accessibility features of languages such as HTML, CSS and SMIL. Like "User Agent Accessibility Guidelines", the current document emphasizes the accessibility of interoperability between two important classes of user agents - graphical desktop browsers and dependent assistive technologies (including screen readers, screen magnifiers, and voice input software). However, it is meant to be applicable to user agents in general, including text and voice browsers, and multimedia players.
While "User Agent Accessibility Guidelines" has been designed to be a stable document of principles, the current document will continue to evolve as technologies change and user agent manufacturers discover more effective techniques for designing accessible user agents.
This document is part of a series of accessibility documents published by the W3C Web Accessibility Initiative.
This is a W3C Working Draft for review by W3C Members and other interested parties. It is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". This is work in progress and does not imply endorsement by, or the consensus of, either W3C or Members of the WAI User Agent (UA) Working Group.
Although the organization of this document has begun to stabilize, the Working Group has not yet filled in the details of all the techniques. This draft does not distinguish those techniques that mainstream user agents are expected to implement natively from those that may be satisfied by providing information through an interface.
This document has been produced as part of the W3C WAI Activity and intends to improve user agent accessibility for all users. The goals of the WAI-UA Working Group are discussed in the WAI UA charter. A list of the current Working Group members is available.
This document is available in the following formats:
http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990309/wai-useragent-tech.html
A plain text file:
http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990309/wai-useragent-tech.txt,
HTML as a gzip'ed tar file:
http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990309/wai-useragent.tgz,
HTML as a zip file (this is a '.zip' file not an '.exe'):
http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990309/wai-useragent.zip,
A PostScript file:
http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990309/wai-useragent-tech.ps,
A PDF file:
http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990309/wai-useragent-tech.pdf.
In case of a discrepancy between the various formats of the specification, http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990309/wai-useragent-tech.html is considered the definitive version.
Please send comments about this document to the public mailing list: w3c-wai-ua@w3.org.
1 Guidelines, Checkpoints, and Techniques
2 The User Agent and the Operating System
3 The User Agent and the Document
3.1 Identification
3.2 Rendering alternative representations of content
3.3 Styles and formatting
4 Functionality offered by the User Agent to allow the User to work with the Document
4.1 Access to all functionality
4.2 Selection and focus
4.3 Navigation
4.4 Searching
4.5 Querying
4.6 Activation
5 The User Agent and the User
5.1 Accessible user interface
5.2 Visibility of accessibility features
5.3 Configuration
5.4 Notification of events and changes
6 The User Agent and Assistive Technologies
7 Support for accessibility features of certain languages
7.3 SMIL
7.4 MathML
8 Appendix: Accessibility features of some operating systems
8.1 Microsoft Windows 95, Windows 98, and Window NT 4.0
8.2 Apple Macintosh Operating System
8.3 AccessX, X Keyboard Extension (XKB), and the X Window System
8.4 DOS (Disk Operating System)
9 Acknowledgments
The guidelines documents have been organized to address readers seeking abstract principles of accessible user agent design and readers seeking concrete solutions. The guidelines documents define three terms for different levels of abstraction:
A guideline is a general principle of accessible design. A guideline addresses the question "What accessibility issues should I be aware of?"
A checkpoint is a specific way of satisfying one or more guidelines. While checkpoints describe verifiable actions that may be carried out by the user agent developer, implementation details are described elsewhere. A checkpoint answers the question "What should I do to improve accessibility?"
A technique is an implementation of one or more checkpoints in a given language (e.g., HTML, XML, CSS, DOM, ...). A technique answers the question "How do I do that in HTML or SMIL or CSS...?"
The current document contains techniques, according to different interfaces between the user agent and the operating system, the document, the user, and other software. Note that each technique in this document is numbered according to its number in the guidelines document.
[Checkpoint 7.2.4] Follow operating system conventions and accessibility settings in user interface design, configuration (including configuration profiles), product installation, and documentation. [Priority 2]
The operating system application programming interfaces (APIs) that support accessibility are designed to provide a bridge between the standard user interface supported by the operating system and alternative user interfaces developed by third-party assistive technology vendors to provide access to persons with disabilities. Applications supporting these APIs are therefore generally more compatible with third-party assistive technology.
The WAI Working Group strongly recommends using and supporting APIs that improve accessibility and compatibility with 3rd party assistive technology. Third-party assistive technology can use the accessibility information provided by the APIs to provide an alternative user interface for various disabilities.
The following is an informative list of currently public APIs that support accessibility:
Microsoft Active Accessibility in Windows 95/NT versions. Information on active accessibility can be found at the Microsoft WWW site on Active Accessibility.
Sun Microsystems Java Accessibility API in Java Code. Information on Java Accessibility API can be found at Java Accessibility Utilities.
Many major operating systems have built-in accessibility features for improving the usability of the standard operating system by persons with disabilities. When designing software that runs above an underlying operating system, developers should ensure that the application:
Makes use of operating system level features. See the appendix of accessibility features for some comment operating systems.
Inherits operating system settings related to accessibility. Pertinent settings include font and color information as well as other pieces of information discussed in this document.
[Ed. We Should put a more exhaustive list here.]
[Checkpoint 4.1.1] Ensure that the software may be installed in a device-independent manner using any supported input and output devices. [Priority 1]
Ensure that software may be installed, when possible, according to the conventions of the operating system.
In order for the user agent to satisfy many of the techniques in this document (related to rendering, notification, navigation, etc.), it must be able to identify certain types of information in addition to recognizing object types such as images, video, sound, and elements of the document language.
Sources of alternative representations of information
User agents must be able to recognize sources of alternative representations of content.
In HTML
For the IMG element: The "alt", "title", and "longdesc" attributes
For the OBJECT element: The content of the element and the "title" attribute.
For the APPLET element: The "alt" attribute and the content of the element.
For the AREA element: The "alt" attribute.
For the INPUT element: The "alt" attribute.
For the ACRONYM and ABBR elements: The "title" attribute may be used for the acronym or abbreviation expansion.
For the TABLE element, the "summary" attribute
For frames, the NOFRAMES element and the "longdesc" attribute on FRAME and IFRAME.
For scripts, the NOSCRIPT element.
In SMIL
The "alt", "title", "longdesc", and "abstract" attributes. To be completed..
Sources of blinking text and animation
User agents that recognize the following sources of blinking text and animations must enable users to freeze that text.
The BLINK element. Note. The BLINK element is not defined by a W3C specification.
The MARQUEE element. Note. The MARQUEE element is not defined by a W3C specification.
In CSS
The 'blink' value of the 'text-decoration' property.
In GIF animated images.
To be completed.
Sources of event handlers
Certain elements of the document language may have associated event handlers that are triggered when certain events occur. User agents must be able to identify those elements with event handlers statically associated (i.e., associated in the document source, not in a script).
All of the attributes beginning with the prefix "on": "onblur", "onchange", "onclick", "ondblclick", "onkeydown", "onkeypress", "onkeyup", "onload", "onmousedown", "onmousemove", "onmouseout", "onmouseover", "onmouseup", "onreset", "onselect", "onsubmit", and "onunload".
[Ed. Other sources? ]
[Ed. To be completed.]
Information about the document
User agents must be able to compute the following information about a document:
Has the document been fully loaded?
What is the size in bytes of the document?
How many active components are in the document?
Where is the point of regard?
Alternative representations of information for images, video, applets
See the section on sources of alternative information
[Checkpoint 5.2.1] Ensure that the user has access to alternative representations of content (e.g., the value of "alt" in HTML or SMIL, the resource designated by "longdesc", or the content of OBJECT in HTML 4.0, the "summary" attribute for tables in HTML, etc.). [Priority 1]
[Checkpoint 5.2.2] When no alternative text representation has been specified, indicate what type of object is present. [Priority 2]
[Checkpoint 5.2.3] When alternative text has been specified explicitly as empty (i.e., an empty string), render nothing. [Priority 3]
Textual equivalents for audio and video
[Checkpoint 5.2.5] Allow the user to specify that captions for audio be rendered at the same time as the audio. [Priority 2]
Scenario-video showing professor writing complex equations and graphs on the overhead and discussing them but not describing what he/she actually wrote on the overhead. Without description this would be inaccessible to people with visual impairments. This could be generalize to any video presentation of visually rich or complex information where the visually presented information is critical to the understanding of the presentation.
[Checkpoint 5.2.8] Allow the user to specify that captions or descriptions for video be rendered at the same time as the video. [Priority 1]
[Checkpoint 5.1.10] Allow the user to control the position of captions. [Priority 1]
Audio equivalents for video
[Checkpoint 5.2.9] Allow the user to specify that audio descriptions of video be rendered at the same time as the video. [Priority 2]
Alternative representations for scripts
In HTML, content of NOSCRIPT.
Alternative representations for frames
[Ed. See Scott's suggestions]
In HTML, content of NOFRAMES.
Otherwise, list of frames. Use "title" as name of frame, otherwise "name".
Alternative representations for tables
In HTML, "summary" attribute. Also, the "abbr" attribute for headers (see the section on table cells and headers).
Generated content
Generated content specified through style sheets can help orient the user. For instance, if, through style sheets, the user can insert the word "Link" before every link, this text may be used by a speech synthesizer or Braille devices. See the section on the support for CSS2 accessibility features below.
[Ed. Based on comments from Jason, add information about UAs allowing users to suppress the rendering of certain elements (e.g., for audio browsers). This can be done with the CSS1 property 'display: none'.]
Properly constructed data tables generally have distinct TH head cells and TD data cells. The TD cell content gains gain implicit identification from TH cells in the same column and/or row.
For layout tables, a user agent can assist the reader by indicating that no relationship between cells should be expected. Authors should not use TH cells just for their formatting purpose in layout tables is discouraged, as those TH cells imply that some TD cells should gain meaning from the TH cell content.
[Checkpoint 5.4.1] Provide access to the contents of a specific table cell. [Priority 1]
When a table is "read" from the screen, the contents of multiline cells may become intermingled. For example, consider the following table:
This is the top left cell    This is the top right cell
table                        of the of the table.
This is the bottom left      This is the bottom right
cell of the table.           cell of the  table.
If read directly from the screen, this table might be rendered as "This is the top left cell This is the top right cell", which would be confusing to the user.
A user agent should provide a means of determining the contents of cells as discrete from neighboring cells, regardless of the size and formatting of the cells. This information is made available through the DOM ([DOM1]).
[Checkpoint 5.4.2] Provide access to header information for a specific table cell. [Priority 1]
The contents of a cell in a data table are generally only comprehensible in context (i.e., with associated header information, row/column position, neighboring cell information etc.). User agents should provide users with header information and other contextual agent. Techniques include:
Provide this information through an API.
Ignore table markup entirely. This may assist some screen readers.
Render cells as blocks. This may assist some screen readers. Using this strategy, the user agent might render individual cells with the relevant top and side headers attached.
Allow navigation and querying of cell/header information. When the point of regard is on an individual cell, the user would be able to use a keyboard command to receive the top and left header information for that cell. The user agent should appropriately account for headers that span multiple cells.
Allow users to read one table column or row at a time, which may help them identify headers.
[Ed. Discuss repair strategies for finding header information?]
Since not all tables are designed with the header information, a conforming user agent should provide, as an option, a "best guess" of the header information for a cell. Possible strategies include:
Consider the top and left-most cells of a column or row to be header information.
Consider upper and left-most cells which have formatting markup to be header information.
The user may choose the form and amount of this information, possibly announcing the row heads only once and then the column head or its abbreviation ("abbr") to announce the cell content.
[Ed. Define algorithm for finding "header information" here. Does it come from THEAD, TH, attributes, HTML 4.0 algorithm for finding header information, etc. Allow the user to choose either "abbr" or what is calculated by the header algorithm.]
Possible solutions:
Provide info through an API.
Frames as blocks.
Frameset as list of links to individual frames (based on frame name).
NOFRAMES content (when?)
[Checkpoint 5.3.6] Provide a mechanism (e.g., through style sheets) to distinguish visited links from unvisited links. [Priority 3]
[Checkpoint 5.3.7] Allow the user to specify (e.g., through style sheets) that images used in links must have borders. [Priority 3]
[Ed. Talk about CSS pseudo-classes for :hover]
[Ed. Talk about using :before to clearly indicate that something is a link (e.g., 'A:before { content : "LINK:" }')]
[Checkpoint 5.5.5] Provide the user with access to any label explicitly associated with a form control. [Priority 2]
[Ed. Talk about "for" attribute for LABEL]
[Ed. Talk about EMBED? Charles recommends that it be put inside an OBJECT if used.]
[Checkpoint 6.1.1] Provide a mechanism for highlighting and identifying (through a standard interface where available) the current view. [Priority 1]
[Checkpoint 6.1.2] Provide a mechanism for highlighting and identifying (through a standard interface where available) the user selection. [Priority 1]
[Checkpoint 6.1.3] Provide a mechanism for highlighting and identifying (through a standard interface where available) the current focus. [Priority 1]
[Checkpoint 6.2.2] Allow the user to view a document outline constructed from its structural elements (e.g., from header and list elements). [Priority 2]
In general, this requirement may be met by providing keyboard access to all functionality and by exposing that functionality to third party technology.
[Checkpoint 6.1.4] Ensure that when the selection changes, it is in the viewport after the change. [Priority 2]
[Checkpoint 6.1.5] Ensure that when the focus changes, it is in the viewport after the change. [Priority 2]
[Checkpoint 6.1.7] Keep track of the user's point of regard in each view and restore it when the user returns to the view. [Priority 1]
There are different ways a user may want to navigate while browsing the Web, including:
By changing the position of the viewport (e.g., by scrolling down the page).
By shifting focus and/or selection from one active component to the next of the same type (e.g., from link to link).
By navigating among documents.
[Ed. Describe tabbing navigation here.]
[Checkpoint 6.1.6] Allow the user to navigate views (notably those with frame viewports). Navigating into a view makes it the current view. [Priority 1]
[Checkpoint 6.2.3] Allow the user to navigate the document tree. [Priority 2]
Document object navigation
[Ed. Discuss tabbing navigation here. How tabbing navigation is specified in HTML: "tabindex".]
[Checkpoint 6.2.1] Allow the user to navigate sequentially among all active elements in the document. See also checkpoints [#Tnav-links], [#Tnav-longdesc], [#Tnav-tables], [#Tnav-form-controls], and [#Tnav-forms]. [Priority 1]
Sequential navigation includes all active elements. User agents might provide other navigation mechanisms limited to a particular type of element. For example "Find the next table" or "Find the previous form". The following checkpoints suggest some types of navigation.
[Checkpoint 5.3.1] Allow the user to navigate sequentially among links. [-Tnav-sequential] [Priority 2]
[Checkpoint 5.5.2] Allow the user to navigate among forms in a document. [-Tnav-sequential] [Priority 2]
[Checkpoint 5.5.1] Allow the user to navigate among form controls within a form. [-Tnav-sequential] [Priority 2]
[Checkpoint 6.3.1] Allow the user to navigate among elements with associated event handlers. [Priority 1]
[Checkpoint 6.2.4] Allow the user to navigate sequentially among headers. [Priority 2]
[Checkpoint 6.2.5] Allow the user to navigate sequentially among block elements (e.g., paragraphs, lists and list items, etc.) [Priority 2]
[Checkpoint 5.3.8] Allow the user to navigate among elements with associated long descriptions. [-Tnav-sequential] [Priority 2]
Table navigation
Users of non-visual rendering technologies and users with learning disabilities, when browsing a page, should be able to quickly determine the nature of a table located on a page. The able-bodied user is able to visually examine the table and extract a sense of the table contents with a quick scan of the cells. A non-visual user, or a user with difficulty translating printed material is not able to do this. Providing table summary information, when first moving the point-of-regard to a table allows the nature of a table to be easily determined.
An auditory rendering agent, when the point-of-regard moves to a table, might say, "Table: Tax tables for 1998," thus identifying the nature of the table. The user could then use keyboard commands to move the point of regard to the next logical block of information, or use a different command to "burrow" into the table.
The "burrow" command should have an opposite "pop" command, which would move the point of regard from an individual cell to the table as a whole, so that the user can leave a table from any cell within it, rather than navigating to the end.
If the user "pops" up to look over the summary information, it should be possible to "burrow" back to the same cell.
When navigating a table that contains another table, this strategy can avoid confusion. For example, if each row of a table contained five cells, but the second row contained a 4x4 table in the third cell, a user could be disoriented when the row did not end as expected. However, when the point of regard moved to the third cell of the table, a compliant browser would report that this was a table, and describe its contents. The user would have the option of navigating to the forth cell of the parent table, or burrowing into the table within this cell.
[Checkpoint 5.4.3] Allow the user to navigate among tables in a document. [-Tnav-sequential] [Priority 2]
When rendering tabular information, the fact that it is tabular information should be apparent. For a visual user agent, such information is commonly made obvious by the border attribute. However, for a non-visual agent, such information must also be made appreciable.
As the user agent shifts the point of regard to a table, it should first provide information about the entire table. This information might be the Caption, Title, or Summary information of the table. Access to this information would allow the user to determine whether or not to examine the contents of the table, or to move the point of regard to the next block of content.
[Checkpoint 5.4.4] Allow the user to navigate among table cells of a table (notably left and right within a row and up and down within a column). [Priority 1]
In many data tables, the meaning of the contents of a cell are related to the contents of adjacent cells. For example, in a table of sales figures, the sales for the current quarter might be best understood in relation to the sales for the previous quarter, located in the adjacent cell.
In order to provide access to contextual information for individuals using non-visual browsers, or for individuals with certain types of learning disabilities, it is necessary for the user agent to allow the point of regard to be moved from cell to cell, both right/left and up/down via keyboard commands.
The most direct method of performing such navigation would be via the cursor keys, though other navigation strategies might be used.
User agents can also help users by allowing them to choose their own navigation patterns, based, for example, on element names, text, attribute values, etc.
[Checkpoint 5.3.2] Allow the user to search for a link in the current document based on its link text. [Priority 1]
[Checkpoint 5.3.3] Allow the user to search for a link based on its attribute values. [Priority 1]
[Checkpoint 5.3.4] Allow the user to move the focus to a link based on its integer (tabbing-order) position. [Priority 1]
[Checkpoint 5.5.3] Allow the user to search for a form control based on its text content. [Priority 1]
[Checkpoint 5.5.4] Allow the user to search for a form control based on its attribute values. [Priority 1]
[Checkpoint 6.2.6] Allow the user to search for content. In case of a match, move the selection to the content. [Priority 2]
[Checkpoint 5.3.9] Allow the user to search linked long description text (i.e., in another document). In case of a match, the focus should be moved to the link in the current document. [Priority 2]
[Checkpoint 5.4.5] Allow the user to search for a table cell based on its contents or header information. [Priority 2]
Users of visual browsers can easily locate cells within a table that are at the intersection of a row and column of interest. To provide equivalent access to users of non-visual browsers, equivalent means of navigation should be provided. The search function of a browser will allow the user to locate key terms within a table, but will not allow the user to find cells that are at the intersection of rows and columns of interest.
An advanced search mode might provide entries for header information, allowing the user to find information at the intersection of columns and rows using the key terms.
A search mode might allow the user to search for key terms that are related to key header terms, allowing searches to be restricted to specific rows or headers within a table.
The header information visible in a TH cell may be abbreviated, in which case it should be user preference to see the "abbr" value if any or the full contents.
Axis information may also help the user search into confined portions of the table.
Column groups and row groups are other confining partitions of a table in which a search may be limited.
[Checkpoint 5.3.5] Provide the user with information about the number of links in a document. [Priority 2]
[Checkpoint 5.5.6] Provide the user with information about the number of forms in a document. [Priority 2]
[Checkpoint 5.5.7] Provide the user with information about the number of controls in a form. [Priority 2]
[Checkpoint 5.4.8] Allow the user to find out the number of tables in a document. [Priority 2]
Users of non-visual rendering technologies may wish, on entering a document, to determine the degree to which tables are used on the page. This information may allow the user to make guesses about the nature of the tables included (layout or data), and to relocate information that was previously browsed.
[Checkpoint 5.4.6] Allow the user to select a table cell and find out its row/column coordinates in the table. [Priority 2]
Non-visual rendering of information by a browser or an assistive technology working through a browser will generally not render more than a single cell, or a few adjacent cells at a time. Because of this, the location of a cell of interest within a large table may be difficult to determine for the users of non-visual rendering.
In order to provide equivalent access to these users, compliant browsers should provide a means of determining the row and column coordinates of the cell having the point of regard via keyboard commands. Additionally, to allow the user of a non-visual rendering technology to return to a cell, the browser should allow a means of moving the point of regard to a cell based on its row and column coordinates.
At the time the user enters a table, or while the point of regard is located within a table, the user agent should allow an assistive technology to provide information to the user regarding the dimensions (in rows and columns) of the table. This information, in combination with the summary, title, and caption, can allow the user with a disability to quickly decide whether to explore the table of skip over it.
[Checkpoint 5.4.7] Allow the user to find out the dimensions of a table. [Priority 2]
Dimensions is an appropriate term, though dimensions needn't be constants. For example a table description could read: "4 columns for 4 rows with 2 header rows. In those 2 header rows the first two columns have "colspan=2". The last two columns have a common header and two subheads. The first column, after the first two rows, contains the row headers.
Some parts of a table may have 2 dimensions, others three, others four, etc. Dimensionality higher than 2 are projected onto 2 in a table presentation.
[Checkpoint 6.1.9] When a document is loaded or when requested by the user, make available document summary information. [Priority 2]
[Ed. What does summary information include?]
[Checkpoint 6.1.8] Provide the user with information about the number of viewports. [Priority 2]
[Checkpoint 6.1.10] Provide the user with information about how much of the document has been viewed (i.e., where the point of regard is with respect to the beginning of the document). [Priority 2]
[Checkpoint 4.3.2] Ensure that user can find out about all keyboard bindings (e.g., through menus). [Priority 2]
[Checkpoint 4.2.3] Ensure that the user can activate the links and form controls in a document in an input device-independent manner. [Priority 1]
[Checkpoint 4.2.1] Ensure that all functionalities offered by the user agent interface are available through all supported input devices. These include the installation procedure, access to documentation, and software configuration. [Priority 1]
[Checkpoint 4.2.2] Ensure that all messages to the user (e.g., warnings, errors, etc.) are available in an output device-independent manner using any supported output devices. [Priority 1]
Universal design means that access to features that help accessibility should be integrated into normal menus. User agents should avoid regrouping access to accessibility features into specialized menus. Documentation includes anything that explains how to install, get help for, use, or configure the product. Users must have access to installation information, either in electronic form (diskette, over the Web), by fax, or by telephone.
[Checkpoint 4.1.3] Describe product features known to promote accessibility in a section of the product documentation. [Priority 2]
For instance, include references to accessibility features in these places:
Indexes. Include terms related to product accessibility in the documentation index (e.g., "accessibility", "disability" or "disabilities").
Tables of Contents Include terms related to product accessibility in the documentation table of contents (e.g., features that promote accessibility)
Include instructions on how to modify all user configurable defaults and preferences (e.g, images, video, style sheets, and scripts) as specified by the documentation.
Include a list of all keyboard shortcuts in the accessibility section of the documentation.
[Checkpoint 4.1.2] Ensure that all product documentation conforms to the Web Content Accessibility Guidelines ([WAI-PAGEAUTH]). [Priority 1]
Documentation created in HTML should follow the Web Content Accessibility Guidelines.
Electronic documentation created in open standard formats such as HTML and ASCII can often be accessed in the user's choice of application such as a word processor or browser. Accessing documentation in familiar applications is particularly important to users with disabilities who must learn the functionalities of their tools, be able to configure them for their needs, and to be compatible with assistive technology. Electronic documentation should not be provided in proprietary formats.
Users with print impairments may need or desire documentation in alternative formats such as Braille, large print, or audio tape. User agent manufacturers may provide user manuals in alternative formats. Documents in alternative format documents can be created by agencies such as Recording for the Blind and Dyslexic and the National Braille Press.
User instructions should be created in an input device-independent manner. Provide instructions for using or configuring the user agent in a manner that can be understood by a user of any input device including a mouse or keyboard. For example, "Click on the Home button on the toolbar or select "Home" from the Go menu to return to the Home page. "
[Checkpoint 4.3.3] Provide a mechanism to render the presence of a keyboard binding for an active element. [Priority 2]
User control of style
To ensure accessibility, users must have final control over certain renderings.
For text and color:
[Checkpoint 5.1.1] Allow the user to control font family. [Priority 1]
[Checkpoint 5.1.2] Allow the user to control font size. [Priority 1]
[Checkpoint 5.1.3] Allow the user to control foreground color. [Priority 1]
[Checkpoint 5.1.4] Allow the user to control background color. [Priority 1]
[Checkpoint 5.1.5] Allow the user to control selection highlighting (e.g., foreground and background color). [Priority 1]
[Checkpoint 5.1.6] Allow the user to control focus highlighting (e.g., foreground and background color). [Priority 1]
[Ed. These may be rendered in a variety of ways. How do we specify rendering?]
For images, applets, and animations:
[Checkpoint 4.4.2] Allow the user to turn on and off rendering of background images. [Priority 1]
[Checkpoint 5.1.7] Allow the user to control animation rate. [Priority 2]
For user agents rendering audio:
[Checkpoint 5.1.11] Allow the user to control audio playback rate. [Priority 1]
[Checkpoint 5.1.12] Allow the user to start, stop, pause, and rewind audio. [Priority 2]
[Checkpoint 5.1.13] Allow the user to control audio volume. [Priority 2]
[Checkpoint 5.2.7] If a technology allows for more than one audio track for video, allow the user to choose from among tracks. [Priority 1]
[Checkpoint 5.2.4] If a technology allows for more than one caption or description track for audio, allow the user to choose from among tracks. [Priority 1]
For user agents rendering video:
[Checkpoint 5.1.8] Allow the user to control video frame rates. [Priority 1]
[Checkpoint 5.1.9] Allow the user to start, stop, pause, and rewind video. [Priority 2]
[Checkpoint 5.2.6] If a technology allows for more than one caption or description track (e.g., text, video of sign language, etc.) for video, allow the user to choose from among tracks. [Priority 1]
For user agents rendering speech:
[Checkpoint 5.1.15] Allow the user to control speech volume, pitch, gender and other articulation characteristics. [Priority 2]
[Checkpoint 5.1.14] Allow the user to control speech playback rate. [Priority 1]
User interface:
[Checkpoint 5.1.16] When new windows or user interface components are spawned, allow the user to control window size and position. [Priority 2]
A configuration profile allows users to save their user agent settings and re-apply them easily, which is particularly valuable in an environment where several people may use the same machine.
[Checkpoint 4.1.4] Allow the user to configure the user agent in named profiles that may be shared (by other users or software). [Priority 2]
The user should be able to easily transfer their profiles between installations of the same user agent. One way to facilitate this is to follow operating system conventions for profiles where applicable.
Users should be able to switch rapidly between profiles (or the default settings). This is helpful when:
Several people use the same machine.
A user with a disability is being helped by able-bodied user who may not recognize the information being displayed using the user's profile.
User agents may apply a profile when the user logs in. They may also allow users to apply settings interactively, for example by allowing them to choose from a list of named profiles in a menu.
Sample profiles (based on common usage scenarios) can assist users in the initial set up of the user agent. These profiles can serve as models and may be copied and fine-tuned to mean an individual's particular needs.
Feature control
[Ed. Add note here that while useful to turn off support, say for all images, it's also useful to be able to view one particular image.]
[Checkpoint 4.4.1] Allow the user to turn on and off rendering of images. [Priority 1]
[Checkpoint 4.4.3] Allow the user to turn on and off rendering of video. [Priority 1]
[Checkpoint 4.4.4] Allow the user to turn on and off rendering of sound. [Priority 1]
[Checkpoint 4.4.5] Allow the user to turn on and off rendering of captions. [Priority 1]
[Checkpoint 4.4.6] Allow the user to turn on and off animated or blinking text. [Priority 1]
[Checkpoint 4.4.7] Allow the user to turn on and off animations and blinking images. [Priority 1]
[Checkpoint 4.4.8] Allow the user to turn on and off support for scripts and applets. [Priority 1]
[Checkpoint 4.4.10] Allow the user to turn on and off support for author style sheets. [Priority 1]
[Checkpoint 4.4.9] Allow the user to turn on and off support for user style sheets. [Priority 1]
[Checkpoint 4.4.11] Allow the user to turn on and off rendering of frames. [Priority 2]
[Checkpoint 4.4.12] Allow the user to turn on and off support for spawned windows. [Priority 1]
User agents may:
Allow users to turn of support for spawned viewports entirely
Prompt them before spawning a viewport
For example, user agents may recognize the HTML construct target="_blank" and spawn the window according to the user's preference.
[Checkpoint 4.4.14] Allow the user to turn on and off automatic page refresh. [Priority 3]
Period page refresh can be achieved with the following markup in HTML:
The user agent should allow the user to disable this type of page refresh.
[Checkpoint 4.4.13] Allow the user to turn on and off automatic page forwarding. [Priority 3]
Although no HTML specification defines this behavior formally, some user agents support the use of the META element to refresh the current page after a specified number of seconds, with the option of replacing it by a different URI. Instead of this markup, authors should use server-side redirects (with HTTP).
User agents can provide a link to another page rather than changing the page automatically.
Keyboard configuration
[Checkpoint 4.3.1] Allow the user to configure keyboard access to user agent functionalities. Configuration includes the ability to specify single keystroke commands as well as commands that require keystroke combinations. [Priority 2]
[Ed. Discuss keyboard access here. How access is specified in HTML: "accesskey".]
[Ed. New section. Users must be allowed to control keyboard configuration based on specific needs. For poor motor control, keys far apart. For poor mobility, keys close together. General principle: fewest keystrokes, short distance to move.]
[Checkpoint 6.1.11] Provide the user with information about document loading status (e.g., whether loading has stalled, whether enough of the page has loaded to begin navigating, whether following a link involves a fee, etc.) [Priority 3]
[Checkpoint 6.3.2] Alert the user when scripts or applets are executed. [Priority 2]
[Checkpoint 6.3.3] Provide information about document changes resulting from the execution of a script. [Priority 3]
[Checkpoint 5.5.8] Allow the user to request to be prompted before a form is submitted. [Priority 3]
[Checkpoint 7.2.2] For desktop graphical browsers. Ensure that exported interfaces conform to those specified by a W3C DOM Recommendation. [Priority 1]
Use DOM Level 1 [DOM1] for access to HTML and XML document information. However, as the DOM specification indicates:
The DOM Level 1 does not include mechanisms to access and modify style specified through CSS 1. Furthermore, it does not define an event model for HTML documents. This functionality is planned to be specified in a future Level of this specification.
It is important for user agents to provide access to style and scripting information in a document, so the following techniques should be used to achieve this.
[Checkpoint 7.2.1] For desktop graphical browsers. Export programmatic interfaces to ATs and follow operating system conventions to do so (e.g., Microsoft Active Accessibility, Sun Microsystems Java Accessibility). [Priority 1]
Use standard rather than custom controls when designing user agents. Third-party assistive technology developers are more likely able to access standard controls than custom controls. If you must use custom controls, review them for accessibility and compatibility with third-party assistive technology.
[Checkpoint 7.2.3] Use standard interfaces defined for the operating system. [Priority 1]
For instance, software should use the standard interface for keyboard events rather than working around it.
[Ed. Integrate Charles' notes on accessibility features of HTML. Sort by priority. See his list of key elements.]
[Checkpoint 7.1.1] Support accessibility features defined by W3C Recommendations for HTML. [Priority 1]
Support the "longdesc" attribute defined for IMG elements ([HTML 4.0], section 13.2). This attribute may be used to attach additional descriptive information to images. [Priority 1]
Support the CAPTION element ([HTML40], section 11.2.2) for rich table captions. [Priority 2]
Support the ACRONYM and ABBR elements ([HTML40], section 9.2.1) for acronyms and abbreviations. [Priority 2]
Support the "summary" attribute for TABLE ([HTML40], section 11.2.1) for table summary information. [Priority 2]
Support the NOSCRIPT element ([HTML40], sections 18.3.1 and 16.4.1) for accessible alternatives to scripts. [Priority 2]
Support the NOFRAMES element ([HTML40], sections 18.3.1 and 16.4.1) for accessible alternatives to frames. [Priority 2]
Support the "lang" attribute ([HTML40], section 8.1). [Priority 2]
Support the "tabindex" attribute ([HTML40], section 17.11.1) for assigning the order of keyboard navigation within a document. [Priority 3]
Support the "accesskey" attribute ([HTML40], section 17.11.2) for assigning keyboard commands to active components such as links, and form controls. [Priority 3]
[Checkpoint 7.1.2] Support accessibility features defined by W3C Recommendations for CSS. [Priority 1]
The following techniques apply to user agents that implement Cascading Style Sheets (see CSS, level 1 and CSS, level 2). Cascading Style Sheets may be part of a source document or linked externally.
Stand-alone style sheets are useful for implementing user profiles in public access computer environments where several people use the same computer. User profiles allow for convenient customization and may be shared by a group.
Completely implement Cascading Style Sheets, level 1 [Priority 1]
Allow the user to turn off author styles represented by author style sheets. [Priority 1]
Allow the user to adjust default values represented by user agent style sheets. [Priority 1]
Support the :before and :after pseudo-elements as defined in CSS2 ([CSS2], section 12.1). [Priority 1]
Support the 'outline' property as defined in CSS2 ([CSS2], section 18.4). Outlines may be used to customize the focus display. [Priority 1]
Allow the user to specify user styles through style sheets (see [CSS2], section 6.4). [Priority 2]
Implement the !important rule as defined in CSS2 ([CSS2], section 6.4.2). These rules offer a way for users to override author styles and user agent defaults [Priority 2]
Support aural cascading style sheets (see [CSS2], chapter 19) for the auditory presentation of documents. [Ed. Expand this into individual properties. Also add 'speak-header'.][Priority 2]
[Checkpoint 7.1.3] Support accessibility features defined by W3C Recommendations for SMIL. [Priority 1]
[Ed. Ensure that in SMIL, users can stop temporal links. See proposal from Marja.]
Several of the more popular mainstream operating systems now include a common suite of built-in accessibility features that are designed to assist individuals with varying abilities. Despite operating systems differences, the built-in accessibility features use a similar naming convention and offer similar functionalities, within the limits imposed by each operating system (or particular hardware platform).
The following is a list of built-in accessibility features from several platforms:
StickyKeys
These allow users to perform a multiple simultaneous key sequence by pressing and releasing each key in sequential order. StickyKeys is designed to work with only those keys defined as modifier keys. Modifier keys are pressed in combination with other keys, to change the outcome of the second (or more) pressed keys. For example, the SHIFT key is defined as a modifier key, since it is commonly used to create upper case characters. Each operating system or hardware platform typically defines a set of keys which can act as modifier keys. The most common modifier keys include SHIFT, CONTROL, and ALTERNATE.
MouseKeys
These allow users to move the mouse cursor and activate the mouse button(s) from the keyboard.
RepeatKeys
These allow users to set how fast a key repeats (e.g., sometimes referred to as typematic rate) when the key is held pressed (e.g., Repeat Rate), and also allows control over how quickly the key starts to repeat after the key has been pressed (e.g., delay Until Repeat). Key repeating may also be eliminated.
SlowKeys
These instruct the computer not to accept a key as pressed until it has been pressed and held down for a specific user adjustable length of time.
BounceKeys
These prevent extra characters from being typed if the user bounces (e.g., tremor) on the same key when pressing or releasing it.
ToggleKeys
These provide an audible indication for the status of keys that have a toggled state (e.g., keys that maintain status after being released). The most common toggling keys include Caps Lock, Num Lock, and Scroll Lock.
SoundSentry
These monitor the operating system and applications for sounds, and attempt to provide a visual indication when a sound is being played. Older versions of Sound Sentry may have flashed the entire display screen for example, while newer versions of SoundSentry provide the user with a selection of options, such as flashing the active window or flashing the active window caption bar.
The next three built in accessibility features are not as commonly available as the above group of features, but are included here for definition, completeness, and future compatibility.
ShowSounds
These are user setting or software switches that are available for the operating system and application (including user agents) APIs to read, to notify them that the user wishes audio information to also be presented in a visual format.
These automatically change the display fonts and colors to choices which should provide for easier reading.
These allow the built-in accessibility features to automatically turn off if the computer is unused for a specified length of time, and is intended for use when the computer is in a public setting (e.g., library). TimeOut might also be referred to as reset or automatic reset.
The next accessibility feature listed here is not considered to be a built in accessibility feature (since it only provides an alternate input channel) and is presented here only for definition, completeness, and future compatibility.
SerialKeys
These allow a user to perform all keyboard and mouse functions from an external assistive device (such as communication aid) communicating with the computer via a serial character stream (e.g., serial port, IR port, etc.) rather than or in conjunction with, the keyboard, mouse, and other standard input devices/methods.
The following accessibility features can be adjusted from the Accessibility Options Control Panel:
StickyKeys: modifier keys include SHIFT, CONTROL, and ALTERNATE
FilterKeys: grouping term for SlowKeys, RepeatKeys, and BounceKeys
MouseKeys:
ToggleKeys:
SoundSentry:
ShowSounds:
Automatic reset: term used for TimeOut
High Contrast:
SerialKeys:
Additional accessibility features available in Windows 98:
This is a windowed, screen enlargement and enhancement program used by persons with low vision to magnify an area of the visual display (e.g., by tracking the text cursor, focus, etc.). Magnifier can also invert the colors used by the system within the magnification window.
Accessibility Wizard
This is a setup tool intended to assist a person with making choices which setting up the accessibility features on a workstation.
The following accessibility features can be adjusted from the Easy Access Control panel (Note: Apple convention uses a space within the accessibility feature names.)
Sticky Keys: modifier keys include the SHIFT, OPEN APPLE (COMMAND), OPTION (ALT) and CONTROL keys.
Slow Keys:
Mouse Keys:
The following accessibility features can be adjusted from the Keyboard Control Panel.
Key Repeat Rate (e.g., part of RepeatKeys)
Delay Unit Repeat (e.g., part of RepeatKeys)
The following accessibility feature can be adjusted from the Sound or Monitors and Sound Control Panel (depends upon which version of the OS).
Adjusting the volume to off or mute causes the Macintosh to flash the title bar whenever the operating system detects a sound (e.g., SoundSentry)
Additional accessibility features available for the Macintosh OS:
CloseView
This is a full screen, screen enlargement and enhancement program used by persons with low vision to magnify the information on the visual display, and it can also change the colors used by the system.
This is available as freeware from Apple and several other Web sites.
(Note: AccessX became a supported part of the X Window System X Server with the release of the X Keyboard Extension in version X11R6.1)
The following accessibility features can be adjusted from the AccessX graphical user interface X client on some DEC, SUN, and SGI operating systems. Other systems supporting XKB may require the user to manipulate the features via a command line parameter(s).
StickyKeys: modifier keys are platform dependent, but usually include the SHIFT, CONTROL, and META keys.
RepeatKeys:
SlowKeys:
BounceKeys:
The following accessibility features are available from a freeware program called AccessDOS, which is available from several Internet Web sites including IBM, Microsoft, and the Trace Center, for either PC-DOS or MS-DOS versions 3.3 or higher.
StickyKeys: modifier keys include the SHIFT, CONTROL, and ALTERNATE keys.
Keyboard Response Group: grouping term for SlowKeys, RepeatKeys, and BounceKeys
SoundSentry (incorrectly name ShowSounds):
TimeOut:
Many thanks to the following people who have contributed through review and comment: Paul Adelson, James Allan, Denis Anson, Kitch Barnicle, Harvey Bingham, Olivier Borius, Judy Brewer, Bryan Campbell, Kevin Carey, Wendy Chisholm, David Clark, Chetz Colwell, Wilson Craig, Nir Dagan, Daniel Dardailler, B. K. Delong, Neal Ewers, Geoff Freed, John Gardner, Al Gilman, Larry Goldberg, John Grotting, Markku Hakkinen, Earle Harrison, Chris Hasser, Kathy Hewitt, Philipp Hoschka, Masayasu Ishikawa, Phill Jenkins, Leonard Kasday, George Kerscher, Marja-Riitta Koivunen, Josh Krieger, Catherine Laws, Greg Lowney, Scott Luebking, William Loughborough, Napoleon Maou, Charles McCathieNevile, Masafumi Nakane, Mark Novak, Charles Oppermann, Mike Paciello, David Pawson, Michael Pederson, Helen Petrie, David Poehlman, Michael Pieper, Jan Richards, Hans Riesebos, Joe Roeder, Lakespur L. Roca, Greg Rosmaita, Lloyd Rutledge, Liam Quinn, T.V. Raman, Robert Savellis, Rich Schwerdtfeger, Constantine Stephanidis, Jim Thatcher, Jutta Treviranus, Claus Thogersen, Steve Tyler, Gregg Vanderheiden, Jaap van Lelieveld, Jon S. von Tetzchner, Willie Walker, Ben Weiss, Evan Wies, Chris Wilson, Henk Wittingen, and Tom Wlodkowski,
"CSS, level 1 Recommendation", B. Bos, H. Wium Lie, eds. The CSS1 Recommendation is:
http://www.w3.org/TR/1999/REC-CSS1-19990111.
"CSS, level 2 Recommendation", B. Bos, H. Wium Lie, C. Lilley, and I. Jacobs, eds. The CSS2 Recommendation is:
[DOM1]
"Document Object Model (DOM) Level 1 Specification", V. Apparao, S. Byrne, M. Champion, S. Isaacs, I. Jacobs, A. Le Hors, G. Nicol, J. Robie, R. Sutor, C. Wilson, and L. Wood, eds. The DOM Level 1 Recommendation is:
http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001.
[HTML40]
"HTML 4.0 Recommendation", D. Raggett, A. Le Hors, and I. Jacobs, eds. The HTML 4.0 Recommendation is:
http://www.w3.org/TR/1998/REC-html40-19980424.
"HTML 3.2 Recommendation", D. Raggett, ed. The HTML 3.2 Recommendation is:
http://www.w3.org/TR/REC-html32.
[MATHML]
"Mathematical Markup Language", P. Ion and R. Miner, eds. The MathML 1.0 Recommendation is:
http://www.w3.org/TR/1998/REC-MathML-19980407.
"Key words for use in RFCs to Indicate Requirement Levels", S. Bradner, March 1997. Available at http://www.ietf.org/rfc/rfc2119.txt
[SMIL]
"Synchronized Multimedia Integration Language (SMIL) 1.0 Specification", P. Hoschka, editor. The SMIL 1.0 Recommendation is:
http://www.w3.org/TR/1998/REC-smil-19980615
[WAI-AUTOOLS]
"Authoring Tool Accessibility Guidelines", J. Treviranus, J. Richards, I. Jacobs, C. McCathieNevile, eds. The latest Working Draft of these guidelines for designing accessible authoring tools is available at:
http://www.w3.org/TR/WD-WAI-AUTOOLS/
[WAI-PAGEAUTH]
"Web Content Accessibility Guidelines", W. Chisholm, G. Vanderheiden, and I. Jacobs, eds. The latest Working Draft of these guidelines for designing accessible Web pages and sites is available at:
http://www.w3.org/TR/WD-WAI-PAGEAUTH.
[XML]
"Extensible Markup Language (XML) 1.0.", T. Bray, J. Paoli, C.M. Sperberg-McQueen, eds. The XML 1.0 Recommendation is:
http://www.w3.org/TR/1998/REC-xml-19980210


Admission season brings loads of students to admission offices. S-Tech has helped a number of universities enhance throughput during admission days with Qmatic. Universities ensure that every person gets their turn and the value if their time is recognised.
Superior University wanted to implement a stand-alone student journey solution to reduce queuing frustrations. They had a goal to boost overall student experience and enable student enquiries to be supported quickly and efficiently in an automated manner. In addition to facilitating students, they also wanted to help staff interact with students in a confidential and relaxed environment.
Qmatic's Solo queue management solution has made it easy for visitors and students to quickly identify where they need to go and how long they will be waiting. Tailored to maximise student flow through the physical space, screens now display queue information indicating where students will be served.
He also added that "Our staff now simply press a button to call the next visitor forward – there's no more leaning over the counter to wave or shout.
Qmatic has helped improve student perception during their inquiries. Fair and equitable queuing process with effective & efficient management has enabled the admissions office to serve up to 800 visitor enquiries a day during peak times. Waiting times have been reduced thanks to a more efficient queue process.
With over 250 campuses all around the country, we strive hard every day to achieve our mission. Our efforts of making Superior University recognized by well-reputed international educational institutions led us to this time when we have more than hundred universities on board with us from across the globe.


text:
MTU Aero Engines Supports Linux Ecosystem
Home|Media|Media Coverage|MTU Aero Engines Supports Linux Ecosystem
September 20, 2022 — For 20 years, MTU Aero Engines has integrated Open Source into its simulation programs and complex algorithms. Germany's largest engine manufacturer has now become a member of OIN's growing worldwide Open Source community. "We support OIN because it's important to us to keep the Linux kernel free of patents and possible lawsuits. The network enables a lot of interaction within the community. By joining, we are saying that we stand behind Linux and want it to stay open," says Dr. Lutz Seidenfaden, CIO of MTU. MRO Business Today shares the story.
Christina Motley2022-09-23T15:19:57-04:00Media Coverage|
We believe the protection OIN offers the open source community helps increase global contributions to and adoption of open source technologies. We are honored to stand with OIN as an active participant in its program to protect against patent aggression in core Linux and other important OSS technologies.
Erich AndersenCorporate Vice President and Chief IP CounselMicrosoft


text:
Second Round Update From the CFSR Team
At the Children's Bureau's annual Agencies and Courts Meeting in August, members of the Federal Child and Family Services Review (CFSR) team presented interim findings from the second round of CFSRs. Data from the 32 reviews completed thus far in this cycle were analyzed to present findings on safety, permanency, and well-being outcomes; systemic factors; and Program Improvement Plans (PIPs).
Safety, Permanency, and Well-Being Outcomes
In conducting the 32 reviews, the CFSR team looked at 2,609 cases, including 1,279 foster care and 790 in-home cases. Among these cases, 52 percent involved male children, 37 percent were cases of neglect, 15 percent involved parental substance use, and 42 percent involved children younger than 6 years.
Case review data were used to determine whether States substantially achieved the safety, permanency, and well-being outcome goals. These were the findings:
Average Percent of Cases Achieving Substantial Conformity Across the 32 States
Safety Outcome 1 (Children are, first and foremost, protected from abuse and neglect) 72 percent
Safety Outcome 2 (Children are safely maintained in their homes when possible and appropriate) 68 percent
Permanency Outcome 1 (Children have permanency and stability in their living situations) 40 percent
Permanency Outcome 2 (The continuity of family relationships and connections is preserved for children) 67 percent
Well-Being Outcome 1 (Families have enhanced capacity to provide for their children's needs) 45 percent
Well-Being Outcome 2 (Children receive appropriate services to meet their educational needs) 87 percent
Well-Being Outcome 3 (Children receive adequate services to meet their physical and mental health needs) 76 percent
The CFSR team made a number of observations about the Outcome data in the cases reviewed, including:
Achievement of Permanency Outcome 1 was positively associated with assessment and provision of services for both children and parents and with caseworker visits with both children and parents.
Across all of the outcomes, performance was stronger in foster care cases than in-home cases.
Mothers generally received more services and visits than fathers across the board.
The CFSR team also provided a number of observations about the composite National Standards, including:
National trends over the last 4 years show an improvement in adoption trends as measured by the composite measure for timeliness of adoptions. This includes an increase in the percentage of children (1) in foster care for 17 months or longer at the start of the reporting year who are discharged to adoption during the year, (2) in foster care for 17 months or longer at the start of the reporting year who became legally free for adoption within 6 months of the reporting year, and (3) legally free for adoption who are adopted in less than 12 months of becoming legally free.
National trends also showed that more children in care for more than 2 years are achieving permanency.
National trends show little change over 4 years regarding children experiencing fewer than 3 moves while in placement.
States were rated on seven systemic factors (SFs), based on whether State performance met Federal requirements. Findings to date from Round 2 show the following:
Systemic Factor
Number of the 32 States Achieving Substantial Conformity
SF 1 (Statewide Information System) 27 States
SF 2 (Case Review System) 1 State
SF 3 (Quality Assurance System) 28 States
SF 4, (Staff and Provider Training) 22 States
SF 5 (Service Array and Resource Development) 8 States
SF 6 (Agency Responsiveness), 31 States
SF 7 (Parent Licensing, Recruitment, and Retention)
No State so far has been rated as a Strength on Item 25 (The State provides a process that ensures that each child has a written case plan to be developed jointly with the child's parents that includes the required provisions), which falls under SF 2 (Case Review System).
Program Improvement Plans
States are required to develop PIPs to address areas of concern noted in their CFSRs. Working with the Children's Bureau, States establish specific amounts of improvement or activities that they will complete within a certain timeline. Thirteen States have already received approval for their Round Two PIPs. Some of the recurrent themes in these plans include:
An emphasis on practice models
Use of evidence-based assessment tools
Stronger worker contacts with families
Implementation of processes such as family team meetings
Enhanced supervision and quality assurance processes
Use of technical assistance through the National Resource Centers
Improved safety assessments
Development of differential response processes
Strengthened diligent search for noncustodial kin
Focus on concurrent planning
Closer review of children who have been in care a long time
Stronger recruitment/retention activities
Development of well-being checklists for use by agencies and courts
Round Two of the CFSRs is still in progress. The Federal CFSR team will continue to gather and analyze data and make the findings available on the CB website when the Final CFSR reports for the remaining 20 States are complete.
Visit the CB website to view the full PowerPoint presentation from August 2009, "Results of the 2007 and 2008 Child and Family Services Reviews":
www.acf.hhs.gov/programs/cb/cwmonitoring/results/index.htm


text:
Q: Degrees of freedom in m(atrix) theory The Hamiltonian for m(atrix) theory is given by
$$H=\frac{1}{2\lambda}\text{Tr}\left(P^{a}P_{a}+\frac{1}{2}\left[X^{a},X^{b}\right]^{2}+\theta^{T}\gamma_{a}\left[X^{a},\theta\right]\right).$$
Where $X^a$ are the $9$ bosonic $N\times N$ matrices and $\theta$ are a $16$-component matrix-valued spinor of $SO(9)$. (Given by Taylor on page 8 in "M(atrix) Theory: Matrix Quantum Mechanics as a Fundamental Theory" at http://arxiv.org/abs/hep-th/0101126).
This can be derived from an action looking like
$$S=\frac{1}{2\lambda}\int\text{d}t\,\text{Tr}\left(\partial_{t}X^{a}\partial_{t}X_{a}-\frac{1}{2}\left[X^{a},X^{b}\right]^{2}+i\theta^{T}\partial_{t}\theta-\theta^{T}\gamma_{a}\left[X^{a},\theta\right]\right)$$.

Since this is a super-symmetric theory the bosonic and fermionic degrees of freedom must match. The equations of motion for the fermions halves the it's degrees if freedom and we are left with only 8. But what about the bosonic degrees, we should have 8 not 9. There is however also a Gauss-constraint given by $\left\{ \partial_{0}X^{I},X_{I}\right\} +\left\{ \theta^{T},\theta\right\} =0$ (which we must impose if we are to have a gauge invariant theory, here the usual gauge field $A$ has been put to zero $A=0$), but this involves both the fermions and bosons and can not only restrict a degree of freedom for the bosonic matrices?
How do I get the bosonic and fermionic degrees of freedom to match?

redpajama_set_name: RedPajamaStackExchange


Psalm 1:1-2 (NIV) [ BOOK I ] [ Psalms 1–41 ] [ Psalm 1 ] Blessed is the one who does not walk in step with the wicked or stand in the way that sinners take or sit in the company of mockers, but whose delight is in the law of the Lord, and who meditates on his law day and night.
You have spoken harsh words against me, says the LORD. Yet you say, "How have we spoken against you?" You have said, "It is vain to serve God. What do we profit by keeping his command or by going about as mourners before the LORD of hosts? Now we count the arrogant happy; evildoers not only prosper, but when they put God to the test they escape." Then those who revered the LORD spoke with one another. The LORD took note and listened, and a book of remembrance was written before him of those who revered the LORD and thought on his name. They shall be mine, says the LORD of hosts, my special possession on the day when I act, and I will spare them as parents spare their children who serve them. Then once more you shall see the difference between the righteous and the wicked, between one who serves God and one who does not serve him. See, the day is coming, burning like an oven, when all the arrogant and all evildoers will be stubble; the day that comes shall burn them up, says the LORD of hosts, so that it will leave them neither root nor branch. But for you who revere my name the sun of righteousness shall rise, with healing in its wings. You shall go out leaping like calves from the stall. And you shall tread down the wicked, for they will be ashes under the soles of your feet, on the day when I act, says the LORD of hosts. Remember the teaching of my servant Moses, the statutes and ordinances that I commanded him at Horeb for all Israel. Lo, I will send you the prophet Elijah before the great and terrible day of the LORD comes. He will turn the hearts of parents to their children and the hearts of children to their parents, so that I will not come and strike the land with a curse.
Are any among you suffering? They should pray. Are any cheerful? They should sing songs of praise. Are any among you sick? They should call for the elders of the church and have them pray over them, anointing them with oil in the name of the Lord. The prayer of faith will save the sick, and the Lord will raise them up; and anyone who has committed sins will be forgiven. Therefore confess your sins to one another, and pray for one another, so that you may be healed. The prayer of the righteous is powerful and effective. Elijah was a human being like us, and he prayed fervently that it might not rain, and for three years and six months it did not rain on the earth. Then he prayed again, and the heaven gave rain and the earth yielded its harvest. My brothers and sisters, if anyone among you wanders from the truth and is brought back by another, you should know that whoever brings back a sinner from wandering will save the sinner's soul from death and will cover a multitude of sins.
Lord knows we like to justify our behavior by casting ourselves in a favorable light. We might be bad. But thank God we're not as bad as a friend or a coworker. We might be mean and selfish, but that guy down the street is way worse. Most of us are just like the Pharisee, propping ourselves up on the backs—and at the expense—of others.
Jesus bids us instead to be like the tax collector: "God, be merciful to me, a sinner!" (18:13b). The ancient Greek maxim to know thyself does not ask us to know the motivations of others. The philosophy of the examined life requires that we look at our own actions, our deepest selves, and determine whether we are living into the beliefs we espouse, the faith we proclaim.
When we compare ourselves not to others but to the vision that Jesus has for each of us, we need be less like the Pharisee, preening and crowing, and more like the tax collector, on our knees and praying for mercy.
… Él saca y cuenta su ejército de estrellas; a todas las llama por su nombre… (Isaías 40:26, RVC).
Preocupado por asuntos del trabajo y del hogar, Mateo decidió salir a caminar. La brisa primaveral era encantadora, mientras el inmenso cielo azul se oscurecía y una espesa niebla descendía lentamente sobre el pantano. Las estrellas comenzaban a brillar, anunciando la salida de la luna llena. La ocasión le resultó sumamente espiritual, y pensó: Dios está allí; Él lo hizo.
Algunos miran el cielo nocturno y solo ven la naturaleza. Otros, un dios tan distante y frío como Júpiter. Pero el mismo Dios que «tiene su trono sobre el arco de la tierra», también «saca y cuenta su ejército de estrellas; a todas las llama por su nombre» (Isaías 40:22, 26). Conoce íntimamente su creación.
Este mismo Dios personal le preguntó a su pueblo: «¿por qué dices que tu camino está oculto para el Señor […], alegas que Dios pasa por alto tu derecho?». Dolido, les recordó cuán sabio es buscarlo: «¿Acaso no sabes, ni nunca oíste decir […]? El Señor […] da fuerzas al cansado, y aumenta el vigor del que desfallece» (vv. 27-29).
Tendemos a olvidar fácilmente a Dios. Nuestros problemas no desaparecerán con una caminata, pero sí podemos descansar y estar seguros de que el Señor obra siempre para cumplir sus buenos propósitos. Dice: «Aquí estoy; yo te hice».
Señor, ayúdame a confiar en ti para lo que no conozco.
Debemos dar a Dios el mismo lugar en nuestro corazón que tiene en el universo.
Probleme an der Arbeit und zu Hause machten Matt zu schaffen. Deshalb beschloss er, rauszugehen und ein wenig zu laufen. Der Frühlingsabend lud förmlich dazu ein. Als der unendliche Himmel sich von Blau zu Schwarz färbte, legte sich dichter Nebel über das Land. Sterne begannen zu funkeln und den aufgehenden Mond anzukündigen. Für Matt war es ein tief spiritueller Moment. Er ist da, dachte er. Gott ist da und kann so etwas machen.
Manche Menschen sehen nichts als die Natur, wenn sie in den Abendhimmel schauen. Andere sehen einen Gott, der so kalt und fern ist wie Jupiter. Aber derselbe Gott, der "über dem Kreis der Erde" thront, ruft auch die Sterne "alle mit Namen" (Jes. 40,22.26). Er kennt seine Schöpfung ganz genau.
Und dieser persönliche Gott fragt sein Volk: "Warum sprichst du denn: Mein Weg ist dem Herrn verborgen, und mein Recht geht an meinem Gott vorüber?" Weil er den Kontakt sucht, fordert er sie auf: "Weißt du nicht? Hast du nicht gehört? . . . Er gibt dem Müden Kraft und Stärke genug dem Unvermögenden" (V.27-29).
Danke, Herr, für den Abendhimmel, der uns einen Blick in die Ewigkeit schenkt. Wir können es nicht begreifen, aber wir wissen, sie ist da und du bist da. Hilf uns, dir in allen Dingen zu vertrauen.
Wir sollten Gott denselben Platz in unseren Herzen einräumen, den er im Universum hat.
Расстроенный неурядицами на работе и дома, Мэт решил прогуляться. Вечерний воздух приятно освежал. Бесконечное небо из синего постепенно становилось черным, над лужайкой сгущался туман. Звезды своим блеском возвестили появление на востоке полной луны. «Он здесь, – подумал Мэт, затаив дыхание, – Бог здесь и держит все это».
Некоторые люди смотрят на небо и видят только природу. Другие воспринимают Бога таким же далеким и холодным, как, скажем, Юпитер. Но тот же Бог, «Который восседает над кругом земли», также управляет звездами и «выводит воинство их счетом. Он всех их называет по имени» (Ис. 40:22, 26). Он в совершенстве знает Свое творение.
Обращаясь к Своему народу, этот Бог сказал: «Как же говоришь ты, Иаков, и высказываешь, Израиль: "Путь мой сокрыт от Господа, и дело мое забыто у Бога моего»?" Глубоко сочувствуя израильтянам, Бог напоминает им: «Разве ты не знаешь? Разве ты не слышал, что вечный Господь Бог... дает утомленному силу и изнемогшему дарует крепость» (Ис. 40:27-29).
Мы склонны забывать Бога. Проблемы порой действительно бывают серьезными. Однако мы можем найти мир и уверенность в сознании, что Бог всегда действует в нашей жизни, преследуя благие цели. «Я здесь, – говорит Он, – Я держу тебя».
Благодарим Тебя, Господь, за ночное небо – отблеск вечности. Мы не можем объять Твоего величия, но мы знаем, что Ты близок к нам. Помоги нам доверить Тебе все, чего мы не понимаем.
Нужно предоставить Богу такое место в сердце, какое Он занимает во вселенной.